Nx operations hangs indefinitely

[JbIPS]

Current Behavior

I'm trying to add Nx to my TS monorepo.

On first try, I installed it (pnpm i nx) but any run would hang on indefinitely. So I removed it, tried to reinstall it but now it hangs at postinstall

node_modules/.pnpm/[email protected]_@[email protected]/node_modules/nx: Running postinstall script

I tried other approach like pnpm dlx nx@latest init or even npx nx@latest init but it hangs at

 NX   🧐 Checking dependencies 

Also tried pnpm dlx create-nx-workspace from scratch but it hangs on the second step

Creating your workspace in test-nx

Expected Behavior

Inits operations should complete gracefully

GitHub Repo

No response

Steps to Reproduce

1. pnpm dlx create-nx-workspace

Nx Report

❯ pnpm dlx nx report                      
Packages: +115
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 123, reused 111, downloaded 4, added 115, done
.cache/pnpm/dlx/ogenweua4lihpne4pbq6bewrt4/1915f46eda6-1d714/node_modules/.pnpm/[email protected]/node_modules/nx: Running postinstall script, done in 373ms

(...and nothing for at least 20min)

Failure Logs

No response

Package Manager Version

PNPM v9.7.0 or NPM v10.5.0

Operating System

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

Additional Information

A common logs I see with NODE_DEBUG=* on all the nx command is

MODULE 121282: RELATIVE: requested: ./error-types from parent.id /home/******/node_modules/.pnpm/[email protected]_@[email protected]/nod
e_modules/nx/src/project-graph/build-project-graph.js
MODULE 121282: looking for ["/home/*******/node_modules/.pnpm/[email protected]_@[email protected]/node_modules/nx/src/project-graph"]
NET 121243: pipe true /tmp/plugin121243-0.sock
NET 121243: connect: attempting to connect to /tmp/plugin121243-0.sock:NaN (addressType: NaN)
MODULE 121282: Module._load REQUEST ./utils/project-configuration-utils parent: /home/*********/node_modules/.pnpm/[email protected]_@swc+
[email protected]/node_modules/nx/src/project-graph/build-project-graph.js
MODULE 121282: RELATIVE: requested: ./utils/project-configuration-utils from parent.id /home/*******/node_modules/.pnpm/[email protected].
7_@[email protected]/node_modules/nx/src/project-graph/build-project-graph.js
MODULE 121282: looking for ["/home/*********/node_modules/.pnpm/[email protected]_@[email protected]/node_modules/nx/src/project-graph"]
NET 121243: createConnection [
  { path: '/tmp/plugin121243-1.sock' },
  [Function (anonymous)],
  [Symbol(normalizedArgs)]: true
]

The addressType: NaN caught my eyes but I don't know if it's relevant. But this logs keeps repeating until it hangs on

MODULE 121275: looking for ["/home/*******/node_modules/.pnpm/[email protected]_@[email protected]/node_modules/nx/src/plugins/js"]
MODULE 121275: Module._load REQUEST child_process parent: /home/*******/node_modules/.pnpm/[email protected]_@[email protected]/node_modul
es/nx/src/plugins/js/index.js
MODULE 121275: load built-in module child_process
STREAM 121243: push <Buffer 7b 22 74 79 70 65 22 3a 22 6c 6f 61 64 2d 72 65 73 75 6c 74 22 2c 22 70 61 79 6c 6f 61 64 22 3a 7b 22 6e 61 6d 65 22 3a 2
2 6e 78 2f 6a 73 2f 64 65 70 ... 205 more bytes>
TIMER 121243: unenroll: list empty
STREAM 121243: maybeReadMore read 0
STREAM 121243: read 0
STREAM 121243: need readable true
STREAM 121243: length less than watermark true
STREAM 121243: do read
NET 121243: _read - n 16384 isConnecting? false hasHandle? true

I tried emptying /tmp, restarting, nx clean but the issue persists

[cefeboru]

Not sure if the issue is related, but I get a similar behavior when upgrading from NX 18 to NX 19. My installation gets stuck on the postinstall nx step forever. If I ignore the scripts when installing modules, subsequent nx commands get stuck as well.

Using:
Node v18.16.0
PNPM 8.12.1
OS Sonoma 14.4.1 (23E224)
Apple M1 Pro

[DanLatimer]

We have some members of our team experiencing this issue too, one reverted to the last version of nx we were on (19.2.3) to get around this fail to install. Would be great to get a fix for this.

[FrozenPandaz]

This occurs on create-nx-workspace for you? Which answers did you provide to the prompts? If possible, is there a repo that I can run nx init in to reproduce the issue?

Can you also see if any of these environment variables resolve the issue?

• NX_DAEMON=false
• NX_ISOLATE_PLUGINS=false

[JbIPS]

It try create-nx-workspace with the env vars, same result

❯ NX_DAEMON=false NX_ISOLATE_PLUGINS=false pnpm dlx create-nx-workspace
Packages: +56
++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 56, reused 55, downloaded 1, added 56, done

 NX   Let's create a new workspace [https://nx.dev/getting-started/intro]

✔ Where would you like to create your workspace? · test-nx
✔ Which stack do you want to use? · none
✔ Package-based monorepo, integrated monorepo, or standalone project? · integrated
✔ Which CI provider would you like to use? · gitlab

 NX   Creating your v19.6.1 workspace.

✔ Installing dependencies with pnpm
⠏ Creating your workspace in test-nx
[Hangs indefinitely...]

I tried to use what seems like basic option to remove complexity but nothing changed.

[blacksand]

I have the same problem, both create-nx-workspace and nx migrate stop responding at postinstall.

The last version that worked is v19.4.4

MacBookPro intel cpu
node: 20.16.0
pnpm: 9.6.0

[github-actions]

This issue has been automatically marked as stale because no reproduction was provided within 7 days.
Please help us help you. Providing a repository exhibiting the issue helps us diagnose and fix the issue.
Any time that we spend reproducing this issue is time taken away from addressing this issue and other issues.
This issue will be closed in 21 days if a reproduction is not provided.
If a reproduction has been provided, please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[tonivj5]

I've suffered from this issue in bitbucket pipelines... 😕 Sometimes it takes so many time to run postinstall

[Markus-Ende]

this is the same: #20270

[github-actions]

This issue has been automatically marked as stale because no reproduction was provided within 7 days.
Please help us help you. Providing a repository exhibiting the issue helps us diagnose and fix the issue.
Any time that we spend reproducing this issue is time taken away from addressing this issue and other issues.
This issue will be closed in 21 days if a reproduction is not provided.
If a reproduction has been provided, please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[90dy]

Related issues:

• Hangs when pnpm install at postinstall #27056
• Nx Reset and other commands that require project graph fail when daemon experiences an error #27220

[keriati]

Similar issue: #28148

[lennybakkalian]

I have the same problem with pnpm/npm/yarn.
It works on my second mac with the exact same repository and node version, so it must be something outside the repository. - Thats prob the reason why no one can reproduce this bug.

NX 19.8.2, Node v20.17.0, PNPM 9.11.0, Apple M2 Pro

Edit:
I have found a workaround:
if i move the project to the /tmp folder and run pnpm i from there, it seems to work.

although i killed all processes accessing files in the project with lsof, the postinstall script only works in /tmp because the files are magically not locked in get_files. unfortunately the nx setup is too complex for me to debug it myself.

[github-actions]

This issue has been automatically marked as stale because no reproduction was provided within 7 days.
Please help us help you. Providing a repository exhibiting the issue helps us diagnose and fix the issue.
Any time that we spend reproducing this issue is time taken away from addressing this issue and other issues.
This issue will be closed in 21 days if a reproduction is not provided.
If a reproduction has been provided, please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[tonivj5]

Up

[github-actions]

This issue has been automatically marked as stale because no reproduction was provided within 7 days.
Please help us help you. Providing a repository exhibiting the issue helps us diagnose and fix the issue.
Any time that we spend reproducing this issue is time taken away from addressing this issue and other issues.
This issue will be closed in 21 days if a reproduction is not provided.
If a reproduction has been provided, please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[aagnone3]

Bump

[mfisher87]

Perhaps we should create a new issue for the one cause we know of and can repro, and leave this issue open for the other potential causes?

[navarrovmn]

Leaving this here as it might help someone else. I also thought I didn't have any .gitignore above my nx repo, but it turns out I had one in my home (~/.gitignore) with the * content that was created by venv (another tool altogether).

After I erased that .gitignore, the command stopped hanging.

[ptrpiero]

Leaving this here as it might help someone else. I also thought I didn't have any .gitignore above my nx repo, but it turns out I had one in my home (~/.gitignore) with the * content that was created by venv (another tool altogether).

After I erased that .gitignore, the command stopped hanging.

Yes I had the same issue! Thank you for pointing it out!

[github-actions]

This issue has been automatically marked as stale because no reproduction was provided within 7 days.
Please help us help you. Providing a repository exhibiting the issue helps us diagnose and fix the issue.
Any time that we spend reproducing this issue is time taken away from addressing this issue and other issues.
This issue will be closed in 21 days if a reproduction is not provided.
If a reproduction has been provided, please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[zblach-postman]

I am able to reproduce this issue with both nx versions 19.6.1 and 20.4.6. the nx postinstall hook hangs indefinitely if there's a .gitignore containing * in a parent directory.

[github-actions]

This issue has been automatically marked as stale because no reproduction was provided within 7 days.
Please help us help you. Providing a repository exhibiting the issue helps us diagnose and fix the issue.
Any time that we spend reproducing this issue is time taken away from addressing this issue and other issues.
This issue will be closed in 21 days if a reproduction is not provided.
If a reproduction has been provided, please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[tonivj5]

Up

a few recent repros:

1. Nx operations hangs indefinitely #27494 (comment)
2. Nx operations hangs indefinitely #27494 (comment)
3. Nx operations hangs indefinitely #27494 (comment)
4. Nx operations hangs indefinitely #27494 (comment) (A docker file!)
5. Nx operations hangs indefinitely #27494 (comment)
6. Nx operations hangs indefinitely #27494 (comment)

automatically closing "stale" issues after only 7 days is a bad practice.

[github-actions]

This issue has been automatically marked as stale because no reproduction was provided within 7 days.
Please help us help you. Providing a repository exhibiting the issue helps us diagnose and fix the issue.
Any time that we spend reproducing this issue is time taken away from addressing this issue and other issues.
This issue will be closed in 21 days if a reproduction is not provided.
If a reproduction has been provided, please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[tonivj5]

Up

a few recent repros:

1. Nx operations hangs indefinitely #27494 (comment)
2. Nx operations hangs indefinitely #27494 (comment)
3. Nx operations hangs indefinitely #27494 (comment)
4. Nx operations hangs indefinitely #27494 (comment) (A docker file!)
5. Nx operations hangs indefinitely #27494 (comment)
6. Nx operations hangs indefinitely #27494 (comment)

automatically closing "stale" issues after only 7 days is a bad practice.

[github-actions]

This issue has been automatically marked as stale because no reproduction was provided within 7 days.
Please help us help you. Providing a repository exhibiting the issue helps us diagnose and fix the issue.
Any time that we spend reproducing this issue is time taken away from addressing this issue and other issues.
This issue will be closed in 21 days if a reproduction is not provided.
If a reproduction has been provided, please reply to keep it active.
Thanks for being a part of the Nx community! 🙏

[Lazerbeak12345]

For the record: this bug is a factor in why I don't use nx right now. I can't honestly tell if the bug is still present (since I don't use it), but this auto-close is very unprofessional. Open source doesn't owe us anything, but I certainly wouldn't pay for this if I knew I could.

[kfarr]

Found this thread after a lot of searching, seems like it's common for this to hang at
NX 🧐 Checking dependencies
after running npx nx init on a project that uses nx as dependency and with node 22?

[ismail-doitbig]

It hangs for me too

After 2 minute I get this:

❯ npm run build:libs

> @zetool/[email protected] build:libs
> nx run-many --target=build --all --verbose --skip-nx-cache

memory allocation of 512 bytes failed

Even if I run nx reset it hangs

❯ npm run reset


> @zetool/[email protected] reset
> nx reset

memory allocation of 512 bytes failed

Even with verbose no output no nothing

It would be nice that it at least gives some console.log("starting x,y,z..") at the beginning when setting --verbose
So I know what it's doing

I'm on Mac M4, using react

[mfisher87]

This issue is closed and likely not being monitored by anyone that can do anything about it. I think a new issue should be created for best chances of this problem being addressed.

[peterbarnett03]

I had the same issue. Mine was simply solved by upgrading Node. I discovered a mismatch when running npm upgrade. Perhaps too simple to be considered "the solution", but it worked for me.

[vivitali]

oh the top support, just close the issue

[vivitali]

I can also confirm that removing/moving the .gitignore in a parent folder to the repo I am trying to setup nx in fixed my issue. The thing that I think is interesting, the .gitignore that was causing issues for me lived in my user's home folder, multiple levels higher than the repository I was trying to initialize nx in.

/Users/phil/development/{company_name}/{git_repository_name}  <-- This is the git repo I was initializing with nx
/Users/phil/.gitignore                                        <-- This is my .gitignore for my user dotfiles

I use the "dotfiles" approach to synchronize my common laptop configurations across my laptops/workstations and never would have guessed this would have caused this issue.

Thank you @90dy for pointing to that stack overflow question which helped me connect the dots to my dotfiles setup.

I am definitely new to the nx toolset/mindset, but is there a reason that nx would need to crawl directories higher than the folder you are calling nx init inside of?

yes that helped me as well. how it even possible that gitignore could cause like that 🤦 🤦 🤦 🤦

[nhhockeyplayer]

Im seeing intermittent hang like every 3rd or 4th live-reload
running nestjs server
have to kill terminal and restart server when it gets stuck
unsure if its related