## The problem
Issue nrwl/nx#27263 (closed, 80 comments): Overnight, every nx command in a monorepo started printing "The Nx Daemon is unsupported in WebAssembly environments", then got stuck and crashed with a wasm memory allocation failure. Nothing in the repo had changed; the breakage arrived via a dependency update.
## What fixed it
Community-diagnosed root cause: your install is missing OS-specific optional packages. Per commenter damienwebdev, this traces back to an npm behavior where optionalDependencies for other operating systems never make it into package-lock.json when a coworker or bot on a different OS runs npm install. When you then run npm ci locally, the native Nx daemon binary packages are missing and Nx falls back to the wasm build, which fails. The fix: run npm install nx@yourversion yourself on your own machine so your lockfile picks up your OS's optional packages. Do not just delete node_modules and package-lock.json and reinstall: that works, but it also nukes everyone else's locked dependency state.