nx
Nx
GitHub
Nx
Workspace
GitHub
CI Pipeline Executions
Current execution
Failed
wasm-fallback-warning
Timeline
Configuration
Self-Healing CI
Project Graph
Resource Usage
Analysis
Conformance
Runs
Current run
Succeeded
Tasks
Resource Usage
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
fix(core): only flag the wasm runtime as a fallback when the native package is unresolvable Gating the warning on platform and arch alone produces a false positive. WebContainers and StackBlitz report linux/x64 and install @nx/nx-linux-x64-gnu normally, but dlopen fails there, so nx correctly runs WASM. Every StackBlitz boot printed a broken lockfile diagnosis that did not apply, and nx report called the runtime a fallback for the same reason. Gate both surfaces on the signature of the install this actually targets: the expected native package cannot be resolved at all. A package that resolves but will not load is left alone, as is NAPI_RS_FORCE_WASI and any platform outside the prebuilt matrix. Only a MODULE_NOT_FOUND counts as absent, so any other resolution error is treated as present and stays quiet. The expected package name and the resolvability probe are shared between the startup warning and nx report so the two cannot disagree. The report field is now a neutral native or wasm, and only appends (missing <package>) under that same predicate.
nx-cloud record -- pnpm nx-cloud conformance:check
⌘K
Succeeded
nx-cloud record -- pnpm nx-cloud conformance:check
Click to copy
Linux
4 CPU cores
3f6978dd
36596
No resource usage was collected for this run.