The Nx Daemon is unsupported in WebAssembly environments

[yannick-bonnefond]

Current Behavior

Starting from this morning any nx commands display the following message on my monorepo, then get stuck for while and fails with the following error

The Nx Daemon is unsupported in WebAssembly environments. Some things may be slower than or not function as expected

memory allocation of 1073741824 bytes failed
wasm://wasm/00b1b546:1


RuntimeError: unreachable
    at wasm://wasm/00b1b546:wasm-function[3313]:0x245577
    at wasm://wasm/00b1b546:wasm-function[3235]:0x24532e
    at wasm://wasm/00b1b546:wasm-function[3249]:0x2453a4
    at wasm://wasm/00b1b546:wasm-function[3123]:0x244de2
    at wasm://wasm/00b1b546:wasm-function[3135]:0x244e7f
    at wasm://wasm/00b1b546:wasm-function[3134]:0x244e74
    at wasm://wasm/00b1b546:wasm-function[3131]:0x244e4f
    at wasm://wasm/00b1b546:wasm-function[2919]:0x243a70
    at wasm://wasm/00b1b546:wasm-function[1894]:0x224274
    at wasm://wasm/00b1b546:wasm-function[1221]:0x1f2606

I also try to run npx create-nx-workspace to test a fresh install and got the same result. Node dependencies are properly installed but the subsequent nx commands fails.

The Nx Daemon is unsupported in WebAssembly environments message comes from the daemon client and it seems that IS_WASM here detects a wasm32 arch for some reason

I guess this issue might be specific to my local setup and I am not sure what have changed since I last run an nx commands (maybe a few days ago).

Let me know if I can provide any additional information.
Thanks for the help

Expected Behavior

nx commands to run successfully

GitHub Repo

No response

Steps to Reproduce

1. run npx create-nx-workspace

Nx Report

Running `npx nx report` yield the same issue

Failure Logs

No response

Package Manager Version

npm:10.2.4

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

System Version: macOS 14.5 (23F79)
Kernel Version: Darwin 23.5.0
Node version 20.11.1

[yannick-bonnefond]

Rolling back to version 19.4.4 seems to fix the issue.

thanks @nathanqtlv for spotting it

[yan-loong]

same issue on windows 11

[ardabeyazoglu]

I have the same issue on windows 11 and wsl2 today with 19.5.6. Downgrading to 19.4.4 did not work either. Strange thing is that it was working today, until an hour ago although i did not change anything.

NX   Failed to process project graph. Run "nx reset" to fix this. Please report the issue if you keep seeing it. See errors below.

Failed to process project graph. Run "nx reset" to fix this. Please report the issue if you keep seeing it.
  An error occurred while processing files for the @nx/vite/plugin plugin.
    - apps/main/vite.config.ts: Cannot find module @rollup/rollup-win32-x64-msvc. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
      Error: Cannot find module @rollup/rollup-win32-x64-msvc. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
          at requireWithFriendlyError (Q:\Works\***\******\node_modules\rollup\dist\native.js:59:9)
          at Object.<anonymous> (Q:\Works\***\******\node_modules\rollup\dist\native.js:68:76)
          at Module._compile (node:internal/modules/cjs/loader:1358:14)
          at Module._extensions..js (node:internal/modules/cjs/loader:1416:10)
          at Module.load (node:internal/modules/cjs/loader:1208:32)
          at Module._load (node:internal/modules/cjs/loader:1024:12)
          at cjsLoader (node:internal/modules/esm/translators:348:17)
          at ModuleWrap.<anonymous> (node:internal/modules/esm/translators:297:7)
          at ModuleJob.run (node:internal/modules/esm/module_job:222:25)
          at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)
    - apps/mobile/vite.config.ts: Cannot find module @rollup/rollup-win32-x64-msvc. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.

EDIT: Deleting node_modules, package-lock.json and .nx folder, and rerunning npm install solved the issue. No need to downgrade.

[yannick-bonnefond]

On my end, since it happens when running npx create-nx-workspace there are no node_modules, package-lock.json or .nx folder to clean up.

Running npm cache clear --force does not resolve the issue either.

[GlebUrentsev]

same issue on macOS 12.7.1
"nx": "19.5.4"

Rolling back to version 19.4.4 seems to fix the issue too

But I'm confused, because I've tested the same project on other setups and didn't get this error (tested on m2, m3 apple chips, macOS 14+)

[thilohaas]

same issue for our setup. rolling back to v19.5.5 fixed the issue.

[danrex]

Deleting node_modules, package-lock.json and .nx folder, and rerunning npm install

This also worked for me on macOS 14+ without downgrading.

[BergLucas]

Same issue on Fedora 40.

[yannick-bonnefond]

I wonder if this issue could be caused by security software somehow preventing memory allocation by Rust code. (I've noticed that the SWC npm post-install script hangs as well, might be related).

I observed that a security software process on my machine shows CPU activity correlated with running the nx command.

• Before running the nx command, the security software's CPU usage is around 0.2%.
• While running the nx command, the security software process spikes to 3% CPU usage, and the nx command's node child process jumps to 99%.
• Both processes remain at these CPU levels until I kill the node process, after which the security software's CPU usage returns to 0.2%.

I don't have much knowledge about Rust, memory allocation and if a security software can actually cause this, but tight now that's my best bet from what I observe...

@BergLucas, @GlebUrentsev, @thilohaas,
Do you have any security software set up on the machine running the nx command?
Or have you observed any other processes whose behavior correlates with the execution of the nx command?

cc @FrozenPandaz

[BergLucas]

Hi @yannick-bonnefond,

I forgot to say that, in my case, I fixed the error by setting the version of @swc/core to 1.5.7 instead of ~1.5.7 in my project. I have colleagues who had the same problem on Windows and this solved the problem on their machines too so the problem may be related to @swc/core or some packages that depends on it.

[arehmaanmughal]

The Nx Daemon is unsupported in WebAssembly environments. Some things may be slower than or not function as expected.
Cannot find project 'react-store'

Node : 22.4.0
OS : win32-x64
Native Target : wasm32
npm : 10.8.1

nx (global) : 19.6.1
nx : 19.6.1
@nx/js : 19.6.1
@nx/jest : 19.6.1
@nx/linter : 19.6.1
@nx/eslint : 19.6.1
@nx/workspace : 19.6.1
@nx/devkit : 19.6.1
@nx/eslint-plugin : 19.6.1
@nx/next : 19.6.1
@nx/react : 19.6.1
@nrwl/tao : 19.6.1
@nx/web : 19.6.1
@nx/webpack : 19.6.1
typescript : 5.5.4

[MilanKovacic]

Possibly related to #22870?

[stefantrost]

I had the same problem with nx version 19.5.2. in my case just reinstalling the node modules (npm ci) did the trick.

Node : 20.15.1
OS : darwin-arm64
npm : 10.7.0
nx : 19.5.2

[shibin-mre]

I transferred a project from my personal laptop to my company laptop. When I try to serve the app on the company laptop, I encounter an error that did not occur on my personal laptop, where there were no daemon issues either. I am using Windows 11 Pro. Could this issue be related to administrator rights or the Nx version 19.6.2?

npm - 10.8.2
node - 20.15.1

[zackarychapple]

Just ran into this issue and found that we had optionalDependencies that were installing the binaries manually. When we upgraded we forgot to update the binaries that were optionally installed.

[shibin-mre]

Just ran into this issue and found that we had optionalDependencies that were installing the binaries manually. When we upgraded we forgot to update the binaries that were optionally installed.

Did you resolve the issue by manually installing the optional Dependencies ?

[zackarychapple]

Did you resolve the issue by manually installing the optional Dependencies ?

Already had them due to CI/CD needs.

[KaliaHayes]

Personally, this issue is only coming when using the Nx VSC Extension. I am able to manually run npx nx run angular-monorepo:serve w/o issues.

[lihongwang]

I fixed this error by install Microsoft Visual C++ 2015 Redistributable (x64)
vc_redist.x64.exe
OS: windows 11

[khoibuda2504]

same problem :(

[jonjnicholson]

I had this same issue on macOS 14.6.1, node 20.17.0, npm 10.8.2

Downgrading to 19.4.4 fixed the issue for me and so did upgrading to 19.6.4

[ussfranck]

NX The Nx Daemon is unsupported in WebAssembly environments. Some things may be slower than or not function as expected.

Same issue on Windows pro 23h2 with PNPM 9.9.0
Blocked for 2 days by this problem, I'm happy to run parallel scripts on all the packages that make up monorepo.

[yan-loong]

Bug Fix: Microsoft Visual C++ Redistributable Update

Issue: After an extended period of troubleshooting, it was identified that the issue was related to an outdated Microsoft Visual C++ Redistributable on Windows systems.

Solution: Ensure that the Microsoft Visual C++ Redistributable is up-to-date. This update resolves compatibility issues and improves overall stability.

Details:
Affected Platform: Windows 11
Download link: https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads

[mdungmc]

I had same issue on Windows 11, node 20.15.1, npm 10.7.1. Pls help me!

[ussfranck]

I had same issue on Windows 11, node 20.15.1, npm 10.7.1. Pls help me!

Hello,
You have this Web Assembly problem because NX needs to rely on certain operating system dependencies to work if you're on Windows, you have to download or update your Microsoft Redistributable C++, on the other hand I'm a Rust developer, so I had to install the C++ environment and thus get all these tools there, the Windows SDK included, when heavy, I don't know if this dependency is mandatory to solve the problem in all it worked on my side.

Concerning the message that web cannot be found in your nx.json, have you checked whether this location is targeted by NX in {projectRoot}/?

Get the latest Microsoft Redistributable C++ on:
https://answers.microsoft.com/en-us/windows/forum/all/looking-for-microsoft-visual-c-2022/ac35251f-6ad9-4dd3-939a-c7c70b1f63b8

[taranjs]

nx serve

 NX   The Nx Daemon is unsupported in WebAssembly environments.
 Some things may be slower than or not function as expected.

The above is what was giving me issues.

The below worked.

npx nx serve

[Rafarel]

Same issue here, a colleague of mine can't work on the project on his Windows 11 machine. (I'm on macOS, and I can't reproduce the problem).
So I cloned our work on my Windows machine to see if I can reproduce it there.
Here is my nx report output :

> nx report

 NX   The Nx Daemon is unsupported in WebAssembly environments. Some things may be slower than or not function as expected.


 NX   Report complete - copy this into the issue template

Node           : 20.13.1
OS             : win32-x64
Native Target  : wasm32
npm            : 10.5.2

nx                 : 19.5.6
@nx/js             : 19.5.6
@nx/jest           : 19.5.6
@nx/linter         : 19.5.6
@nx/eslint         : 19.5.6
@nx/workspace      : 19.5.6
@nx/angular        : 19.5.6
@nx/cypress        : 19.5.6
@nx/devkit         : 19.5.6
@nx/esbuild        : 19.5.6
@nx/eslint-plugin  : 19.5.6
@nx/express        : 19.5.6
@nx/nest           : 19.5.6
@nx/node           : 19.5.6
@nrwl/tao          : 19.5.6
@nx/web            : 19.5.6
@nx/webpack        : 19.5.6
typescript         : 5.4.5
---------------------------------------
Community plugins:
@fortawesome/angular-fontawesome : 0.14.0
ng-extract-i18n-merge            : 2.10.0
ngx-toastr                       : 17.0.2
nx-stylelint                     : 17.1.5

An issue pops from nowhere from time to time, and it really affects the quality of life of the developers who encounter this kind of issues. Tell me if I can help you with that!

On my end I tried to get a fresh git clone, fresh npm i, re-generate the package-lock.json but nothing works.

[Rafarel]

⭐️ Follow-up to my previous message:
We switched from using npm to pnpm, and that fixed the issue!
Does this solve your problem too?

[DzmVasileusky]

Same issue with global nx.

pnpm nx --version

> [email protected] nx /Users/dzmvasilevsky/Work/TulaCo/crexi/web
> nx "--version"

Nx Version:
- Local: v19.8.0
- Global: Not found

pnpm nx report
> nx "report"


 NX   Report complete - copy this into the issue template

Node           : 20.11.0
OS             : darwin-x64
Native Target  : x86_64-macos
pnpm           : 9.11.0

nx                 : 19.8.0
@nx/js             : 19.8.0
@nx/jest           : 19.8.0
@nx/linter         : 19.8.0
@nx/eslint         : 19.8.0
@nrwl/linter       : 13.5.1
@nx/workspace      : 19.8.0
@nx/angular        : 19.8.0
@nx/cypress        : 19.8.0
@nx/devkit         : 19.8.0
@nx/eslint-plugin  : 19.8.0
@nx/playwright     : 19.8.0
@nx/plugin         : 19.8.0
@nx/storybook      : 19.8.0
@nrwl/tao          : 19.8.0
@nx/vite           : 19.8.0
@nx/web            : 19.8.0
@nx/webpack        : 19.8.0
typescript         : 5.5.4
---------------------------------------
Community plugins:
@ngrx/component-store : 18.0.2
@ngrx/effects         : 18.0.2
@ngrx/entity          : 18.0.2
@ngrx/operators       : 18.0.2
@ngrx/router-store    : 18.0.2
@ngrx/schematics      : 18.0.2
@ngrx/store           : 18.0.2
@ngrx/store-devtools  : 18.0.2
@storybook/angular    : 8.2.9
ng-mocks              : 14.13.0

I definitely had global NX installed, I created projects with it. Not sure what happened

[budiadiono]

I fixed this error by install Microsoft Visual C++ 2015 Redistributable (x64) vc_redist.x64.exe OS: windows 11

thank you so much! this solution worked for me!

[GaetanWcz]

Following up.
Recently updated my Mac M1 to Sequoia and cannot operate any Nx command anymore.

[stuurman]

Following up. Recently updated my Mac M1 to Sequoia and cannot operate any Nx command anymore.

Same thing here on Mac M2 when serving an Angular Application.
switching to pnpm seems a workaround to serve the Angular App again.

[ksinghal]

I have the same problem, and nothing is working to fix this. I have completely uninstalled NX and reinstalled, completely removed NPM and Node and reinstalled, tried everything. I removed my local git repo and re-cloned and that worked briefly and then this started happening again. Any solution would be very helpful.

I am on MacOS 15

[GaetanWcz]

So I managed to make my project viable again.

I bumped NX to 20.0.3 through the nx migrate command.
Then I applied the migrations that were needed

I completely removed .nx and node_modules, reinstalled node_modules, nx reset, and it now work as intended.

[Kendru98]

I have the same problem on macOS 14.0. Tried solutions in this thread but nothing works for me :/

[Kendru98]

I did this, and additionally I move repository from external disk to main disk on Mac mini, it helps in my case. Not sure if both things are needed, but one helps for sure ^^

npm install --save-optional
"@swc/core-darwin-arm64"
"@swc/core-darwin-x64"
"@swc/core-linux-arm-gnueabihf"
"@swc/core-linux-arm64-gnu"
"@swc/core-linux-arm64-musl"
"@swc/core-linux-x64-gnu"
"@swc/core-linux-x64-musl"
"@swc/core-win32-arm64-msvc"
"@swc/core-win32-ia32-msvc"
"@swc/core-win32-x64-msvc"

[FadiNouh1]

Same Problem, windows 11 , @nx/angular: 19.8.4

[FadiNouh1]

I had same issue on Windows 11, node 20.15.1, npm 10.7.1. Pls help me!

Hello, You have this Web Assembly problem because NX needs to rely on certain operating system dependencies to work if you're on Windows, you have to download or update your Microsoft Redistributable C++, on the other hand I'm a Rust developer, so I had to install the C++ environment and thus get all these tools there, the Windows SDK included, when heavy, I don't know if this dependency is mandatory to solve the problem in all it worked on my side.

Concerning the message that web cannot be found in your nx.json, have you checked whether this location is targeted by NX in {projectRoot}/?

Get the latest Microsoft Redistributable C++ on: https://answers.microsoft.com/en-us/windows/forum/all/looking-for-microsoft-visual-c-2022/ac35251f-6ad9-4dd3-939a-c7c70b1f63b8

this solved the issue on windows 11

[Dayonel]

Same here on macOS Sonoma 14.2.1 (23C71) M1 serving an Angular application.

[ryanhendry]

I'm running on a locked-down corporate windows 11 laptop for one of my projects and have out of the blue started getting this warning today along with all projects disappearing when running any nx command. I checked in installed apps and already have up-to-date Microsoft Redistributable C++ but I'm going to see if I can reinstall. I actually suspect the security software as has been alluded to above. I haven't tracked down the exact cause and solution yet, but I think something is going on with the security software and NX's use of swc/Rust/WASM

EDIT:

I have solved it in my case, it was security software on Windows blocking the nx-native-file-cache .node file from running.
This line silently (from a user perspective) fails and you get kicked into the wasm32 native binding, which seems completely broken. I solved the issue by getting my IT department to whitelist AppData/Local/Temp/nx-native-file-cache-{wildcard}/{wildcard}.node .

[gzzsound]

It might be helpful in certain circumstances; the issue for me was that, on Apple ARM CPU, I was running an Intel version of Node.

Installing the correct version, removing the node_modules, and re-installing helped.

[claylaut]

I just stumbled into this issue. I updated my node version to 20.18 and it worked fine with the latest NX 20.1.2.

[ghostlydilemma]

For me it happened after a MacOS Update (from 14 to 15.1).

I could somehow fix it by switching from IntelliJ runners to an actual command line...

[ghostlydilemma]

Fix for me was to reinstall node/npm using nvm. I had the x64 version but I am using an ARM Mac. I have no idea why it suddenly decided to break as I haven't changed anything about the setup...

This guide helped me: https://medium.com/@k.auffinger/switching-to-arm-based-node-on-macos-964f89af4264

[Redn4s]

I stumbled upon the same error message on my Mac (M4) with MacOS 15.1 and Node v20.18.0. Nx v20.1.4 fixed it for me.

[martin-tag24]

leaving this as help here what we found:
in our project the package-lock.json was generated by a linux machine, doing just npm install gave all mac machines this error. simply removing the package-lock.json (and node_modules) entirely followed by a new npm install fixed it on all macs.

[usmananwar-1995]

Deleting node_modules, package-lock.json and .nx folder, and rerunning npm install solved the issue. No need to downgrade.

This also worked for me on macOS 15+ without downgrading 🚀

[kasc-fidentity]

I was able to fix it by:

1. Upgrading from macOS 14.x to macOS 15.2
2. Installing the following devDependencies:
3. Removing package-lock.json and node_modules/
4. Re-Running npm i

    "optionalDependencies": {
        "@esbuild/linux-x64": "0.24.0",
        "@rollup/rollup-linux-x64-musl": "4.28.1",
        "@esbuild/darwin-x64": "0.24.0",
        "@rollup/rollup-darwin-x64-musl": "4.28.1",
        "@swc/core-linux-arm-gnueabihf": "^1.10.1",
        "@swc/core-linux-arm64-gnu": "1.10.1",
        "@swc/core-linux-arm64-musl": "1.10.1",
        "@swc/core-linux-x64-gnu": "1.10.1",
        "@swc/core-linux-x64-musl": "1.10.1",
        "@swc/core-darwin-arm64": "1.10.1",
        "@swc/core-darwin-x64": "1.10.1"
    }

[schreibse]

I have solved it in my case, it was security software on Windows blocking the nx-native-file-cache .node file from running.
This line silently (from a user perspective) fails and you get kicked into the wasm32 native binding, which seems completely broken. I solved the issue by getting my IT department to whitelist AppData/Local/Temp/nx-native-file-cache-{wildcard}/{wildcard}.node .

Solved it for me, thank you

[musman-se]

Hi, here's how I fixed it, in case you get the same issue on your end - Windows 11

1. install the nx globally: npm add --global nx@latest
2. run this command on your cmd: set NX_DAEDOM=false
3. then run your project

[hojjatmahdave]

I had same issue on Windows 11, node 20.15.1, npm 10.7.1. Pls help me!

Hello, You have this Web Assembly problem because NX needs to rely on certain operating system dependencies to work if you're on Windows, you have to download or update your Microsoft Redistributable C++, on the other hand I'm a Rust developer, so I had to install the C++ environment and thus get all these tools there, the Windows SDK included, when heavy, I don't know if this dependency is mandatory to solve the problem in all it worked on my side.
Concerning the message that web cannot be found in your nx.json, have you checked whether this location is targeted by NX in {projectRoot}/?
Get the latest Microsoft Redistributable C++ on: https://answers.microsoft.com/en-us/windows/forum/all/looking-for-microsoft-visual-c-2022/ac35251f-6ad9-4dd3-939a-c7c70b1f63b8

this solved the issue on windows 11

it resolved my error on nx about the nx-demon, for the those guys that just installed the windows consider this and install it.

[serg-mois-capital]

I had same issue on Windows 11, node 20.15.1, npm 10.7.1. Pls help me!

Hello, You have this Web Assembly problem because NX needs to rely on certain operating system dependencies to work if you're on Windows, you have to download or update your Microsoft Redistributable C++, on the other hand I'm a Rust developer, so I had to install the C++ environment and thus get all these tools there, the Windows SDK included, when heavy, I don't know if this dependency is mandatory to solve the problem in all it worked on my side.
Concerning the message that web cannot be found in your nx.json, have you checked whether this location is targeted by NX in {projectRoot}/?
Get the latest Microsoft Redistributable C++ on: https://answers.microsoft.com/en-us/windows/forum/all/looking-for-microsoft-visual-c-2022/ac35251f-6ad9-4dd3-939a-c7c70b1f63b8

this solved the issue on windows 11

it resolved my error on nx about the nx-demon, for the those guys that just installed the windows consider this and install it.

Thanks, it helped us as well.

[CameronSend]

Just to throw another potential solution in, I was getting this error because I was starting the application through a bash script, and bash on my system was using WSL rather than Git Bash. Which meant the entire thing was running inside WSL. Once I adjusted my system PATH to favour Git Bash over WSL, the issue went away. Niche, but may help someone.

[KaliaHayes]

leaving this as help here what we found: in our project the package-lock.json was generated by a linux machine, doing just npm install gave all mac machines this error. simply removing the package-lock.json (and node_modules) entirely followed by a new npm install fixed it on all macs.

This worked for me as well - MacOS - nx v20.4.5 - node v22