Run details

NxWorkspace

CI Pipeline Executions
Runs
- Current runSucceeded
- Tasks
- Resource Usage

Insights

Compare tasks
Analytics

Sign in

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 run-many -t check-imports check-lock-files check-codeowners --parallel=1 --no-dte

Succeeded

4 CPU cores

read-write access token used

3f6978dd36596

Get faster results

Learn how to enable distribution.

Atomizer enabled

1 group of tasks optimized.

Machine

4 cores · 15.61 GB

CPU (avg / max)

78.69% / 135.78%

Memory (avg / max)

1.35 GB / 2.19 GB

© 2026 - Nx Cloud

Terms of Service Privacy Policy Changelog Status Docs Contact Nx Cloud Pricing Company @NxDevTools