NX project graph calculation hanging indefinitely

[electrocnic]

Current Behavior

When I created a nx monorepo following the documentation using the single version strategy (where the documentation claims that a package.json is only needed at the workspace root but not for the individual apps), everything worked fine so far, could build the first app which was automatically added by the generator.

I already had issues in the beginning tho, that some nx commands (some plugins perhaps, I used a vite typescript react app with eslint and prettier) failed because they wanted a package.json at the root of the project (meaning the app, not the workspace), so I searched a while online and just added a stupid simple package.json to the app with only the name, the version and nothing else.
It worked again, nx built the project graph and built the app and served it.

After some days I wanted to add a second app to my monorepo.
Directly with the @nx/react generator in the VSCode extension to generate my app.

Settings were:

directory: apps/app2
bundler: vite
linter: eslint
name: myAppName
unitTestRunner: vitest
compiler: babel
e2eTestRunner: none
strict: true
style: tailwind

Once I generated this app, everything began to hang in the VSCode nx console. It tried to refresh the workspace indefinitely.
I started using terminal console commands manually like npx nx reset, npx nx run build:app2 and waited and waited and waited.
Deleted node_modules completely and ran npm i from scratch, installed latest node LTS 22 version on the Windows host machine, restarted the computer, and so on.
Deleted the second app again from the repo and it worked again and built the app.
Re-generated the second app, freeze.
Deleted app2 again, worked again,
Re-generated, freeze again.

Always with Calculating the project graph on the Nx Daemon is taking longer than expected. Re-run with NX_DAEMON=false to see more details. then NX_DAEMON=false npx nx run build:app2 --> hangs at Creating project graph dependencies with 6 plugins.
sometimes just Failed to process project graph. Run "nx reset" to fix this.

Also, any nx command failed, not just for app2, but also for app1.

When I finally figured, the only difference between app1 and app2 was, that the generator did not add a package.json to the freshly created app2, I copied the slim one from app1, renamed the name field for app2 and voila, it worked again.

Content of the package.json on app-level:

{
  "name": "@appX",
  "version": "0.0.0",
  "private": true,
  "dependencies": {}
}

Expected Behavior

• nx commands should not hang up without error messages if package.json files are missing.
• The nx documentation should not falsely claim that, for single-version monorepos, a package.json is not needed per app, but only one per workspace root, which apparently is wrong (at least in my configured setup, where I wanted to have type: module in my workspace root, and with the tools that I used).
• the @nx/react generator should add a package.json to the generated app
• or, if all of this is a wrong configuration on my side, the nx documentation should clearly show how to configure the monorepo with type:module (for ESM type projects (not talking about nx plugins, but about my project code)) without package.jsons in each app folder, because it does not work with this setup, as some plugins will complain about the missing package.json, being it typescript, eslint, vite or something else.

GitHub Repo

No response

Steps to Reproduce

1. in a fresh location npm i -D @nx/react/latest (selecting vite, typescript, eslint, prettier)
2. add "type": "module" to workspace root package.json
3. tsconfig.base.json: "moduleResolution": "bundler", "target": "es2022", "lib": ["es2023", "DOM", "DOM.Iterable"]
   this should be the key changes where trying to build the app produce some "package.json missing" errors.

Nx Report

Node           : 22.13.0
OS             : win32-x64
Native Target  : x86_64-windows
npm            : 11.0.0

nx                     : 20.3.1
@nx/js                 : 20.3.1
@nx/eslint             : 20.3.1
@nx/workspace          : 20.3.1
@nx/devkit             : 20.3.1
@nx/eslint-plugin      : 20.3.1
@nx/module-federation  : 20.3.1
@nx/react              : 20.3.1
@nx/vite               : 20.3.1
@nx/web                : 20.3.1
typescript             : 5.7.3
---------------------------------------
Registered Plugins:
@nx/vite/plugin
@nx/eslint/plugin
@nx/js/typescript

Failure Logs

Package Manager Version

No response

Operating System

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

Additional Information

No response

[thengstermanndev]

Currently facing the same issue. In my case i'm forced to shutdown my computer since this is blowing up my RAM.

I'm using macOS

Edit: In my case removing Nx Console extension from VSCode resolved the issue.

[MajorTom327]

Got something similar.
But in my case, no extension. Running directly the command from the console.
Only one project. The command nx serve app just block on the generating graph thing. But even the nx show project app and the nx report are in the same issue.
Was trying to build a react 19 + vite + react router 7 app in ESM.
No log, no feedback is pretty hard to get any informations on what's going on and find exactly where could be the issue. (Nx side? Vite side? Configuration Side?)

[canibanoglu]

I'm in the same boat, using MacOS, latest version of nx.

What I found out is that if I try to install a package (@llama/chat-ui in this case), things just start to blow up. First I start getting issues from typescript which lead me to make the following changes:

• add "type": "module" to my nx ui library's package.json, not the root one. I'm assuming this fixes the error I get from import { xxx } from "@llama/chat-ui"
• switch moduleResolution from node to bundler.

After those simply gets stuck at graph generation. There's nothing in .nx/workspace-data/d/daemon.log, it's just stuck. Setting NX_DAEMON=false has absolutely no effect.

More information:
This is only happening if I try to import into the ui library components. If I'm doing all of the work within the app project, everything works fine.

[curious-33]

I got the same issue, the process of calculating the project graph is hanging there. I imported an app from another repo and then got this issue:

At first attempt(I mean after I clean the node_modules and clear nx caches), there is no hanging issue. But when I tried to run my local env 2nd time, I got the issue.

The versions of my nx packages:

• "@nrwl/linter": "^19.8.4",
• "@nrwl/vite": "^19.8.4",
• "@nx/eslint": "20.3.1",
• "@nx/eslint-plugin": "20.3.1",
• "@nx/jest": "20.3.1",
• "@nx/js": "20.3.1",
• "@nx/react": "20.3.1",
• "@nx/vite": "20.3.1",
• "@nx/web": "20.3.1",
• "@nx/workspace": "20.3.1",
• "nx": "20.3.1",

[mamun2519]

Currently, I am facing this issue while setting up a new project. I have another existing project using Nx, where everything is working perfectly.
https://i.ibb.co.com/gZNkgr3/Screenshot-from-2025-01-20-09-32-25.png

[studix]

Same issue here.
The versions of nx in my root package.json:

"@ngrx/schematics": "19.0.0",
"@ngrx/store-devtools": "19.0.0",
"@nx/esbuild": "20.3.2",
"@nx/eslint": "20.3.1",
"@nx/eslint-plugin": "20.3.1",
"@nx/jest": "20.3.1",
"@nx/js": "20.3.2",
"@nx/node": "^20.3.2",
"@nx/storybook": "20.3.1",
"@nx/web": "20.3.1",
"@nx/workspace": "20.3.1",
"nx": "20.3.1",

Does anybody know a workaround?

[mmmoli]

Same, in my nx + vite + rr7 app.

Although it seems to be the tailwind config that breaks it:

• Without tailwind, works
• Add tailwind (nx g @nx/react:setup-tailwind --project=<your app here>) and it breaks

[mmmoli]

Same, in my nx + vite + rr7 app.

Although it seems to be the tailwind config that breaks it:

• Without tailwind, works
• Add tailwind (nx g @nx/react:setup-tailwind --project=<your app here>) and it breaks

More investigation. Delete the postcss.config file and it works again. Vite doesn't need it.

[fridezlucas]

Isn't it related to tailwindcss@4.0.0 ? I created a fresh nx workspace with tailwind v4 and this error occured. I switch to tailwind 3 and workspace is now working !

[Lonli-Lokli]

same for me, solved by adding two package,json to both apps (react/next) also facing Projects should use relative imports to import from other files within the same project. while Im importing library code from app code

[kustomq]

We need tailwindcss@4.0.0 support, currently even the guide https://nx.dev/recipes/react/using-tailwind-css-in-react is outdated.