Nx 19.5 cannot find projects after initial creation

[SiKreuz]

Current Behavior

I created a new project with nx g @nx/nest:app backend. Process went through without any errors. However, If I now try to compile, nx tells me it cannot find the projects. Calling nx show projects gives me an empty list.

This happens from version 19.5.0 on. I downgraded to 19.4.4 and there it does work. nx show projects gives me all existing projects. Upgrading back to 19.5.0 lets the projects vanish again

Expected Behavior

I expect a freshly generated project to appear and be found when using nx show projects.

GitHub Repo

No response

Steps to Reproduce

1. bunx create-nx-workspace my-workspace
2. cd my-workspace
3. bun nx add @nx/nest
4. bun nx g @nx/nest:app my-nest-app
5. bun nx show projects

Nx Report

Node           : 22.5.1
OS             : darwin-arm64
Native Target  : aarch64-macos
bun            : 1.1.22

nx                 : 19.5.7
@nx/js             : 19.5.7
@nx/jest           : 19.5.7
@nx/linter         : 19.5.7
@nx/eslint         : 19.5.7
@nx/workspace      : 19.5.7
@nx/devkit         : 19.5.7
@nx/eslint-plugin  : 19.5.7
@nx/nest           : 19.5.7
@nx/node           : 19.5.7
@nrwl/tao          : 19.5.7
@nx/web            : 19.5.7
@nx/webpack        : 19.5.7
typescript         : 5.4.5
---------------------------------------
Registered Plugins:
@nx/webpack/plugin
@nx/eslint/plugin
@nx/jest/plugin

Failure Logs

No response

Package Manager Version

bun 1.1.22

Operating System

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

Additional Information

No response

[pascalmann]

Same problem for me (Ubuntu 20).
Some libs disappear from the project graph.
Nx reset doesn't solve the problem.

• If I save the project.json file of a lib
• nx show projects -> the lib returns in the project graph
• nx reset -> the lib disappear again

[mechanical-fish]

This is probably the bug that just bit me (on MacOS Sonoma 14.6.1)-- because reverting to 19.4.4 also brought back my project graph, whereas 19.5.7 and 19.6.1 just return an empty project graph.

[jaysoo]

I'm not able to reproduce on either 19.5 or 19.6. Can someone link a repro? I'm also on MacOS Sonoma 14.6.1.

Does running with NX_DAEMON=false NX_CACHE_PROJECT_GRAPH=false generate the graph?

[mechanical-fish]

Running with NX_DAEMON=false NX_CACHE_PROJECT_GRAPH=false does not help with Nx 19.5.7. npx nx show projects still returns nothing.

I've just managed to reproduce this on a fresh clone of https://github.com/nrwl/nx-examples with Nx upgraded to 19.6.1. After doing so, npx nx show projects on that repo returns nothing, and NX_DAEMON=false npx nx show-projects hangs indefinitely and has to be terminated with kill -9, leaving behind a whole bunch of plugin-worker processes. Downgrading to 19.4.4 resolves the issue and gives me a list of projects.

I'll try running something like @SiKreuz 's workflow to see if I can find an even more minimal example.

I note that while we have many programmers running laptops set up much like mine, and who have run Nx 19.5.7 on existing working copies of our codebase without a hitch, I'm the first and only one to report this problem. I wish I could guess what I did differently, and why that difference persists on my machine through a reboot, a cleanup of my $HOME directory, a freshly cloned and installed codebase, an entirely new Nx project, etc. (We've now reverted our Nx-equipped codebase to 19.4.4, so this problem probably won't bite anyone else around here.)

[mechanical-fish]

EDIT: I can't get create-nx-workspace to work without hanging even back in nx version 18.3.4, so 🤷

npx create-nx-workspace my-workspace also hangs indefinitely for me with version 19.6.1:

❯ npx create-nx-workspace my-workspace

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

✔ Which stack do you want to use? · none
✔ Package-based monorepo, integrated monorepo, or standalone project? · package-based
✔ Which CI provider would you like to use? · skip
✔ Would you like remote caching to make your build faster? · skip

 NX   Creating your v19.6.1 workspace.

✔ Installing dependencies with npm
⠦ Creating your workspace in my-workspace     

I can stop the install process with ^C but the process list continues to contain three plugin-worker processes, plus these two processes which need to be killed with kill -9:

node nx new --interactive --standaloneApi --routing --no-skipGit --no-g --commit.message=Initial commit --no-allPrompts --no-a --/bin/sh=/Users/mbooth/.npm/_npx/d2207cf76adb22dc/node_modules/.bin/create-nx-workspace --name=my-workspace --stack=none --preset=npm --nxCloud=skip --packageManager=npm --defaultBase=main --nxWorkspaceRoot=/Users/mbooth/Code/vendor/reprobug

npm exec nx new --interactive --standaloneApi --routing --no-skipGit --no-g --commit.message=Initial commit --no-allPrompts --no-a --/bin/sh=/Users/mbooth/.npm/_npx/d2207cf76adb22dc/node_modules/.bin/create-nx-workspace --name=my-workspace --stack=none --preset=npm --nxCloud=skip --packageManager=npm --defaultBase=main --nxWorkspaceRoot=/Users/mbooth/Code/vendor/reprobug  

[mechanical-fish]

we are now at the stage of debugging where I doubt the nature of reality. In a directory with only one file, package.json, with the following contents:

{
  "name": "my-workspace",
  "version": "0.0.0",
  "license": "MIT",
  "scripts": {},
  "private": true,
  "dependencies": {},
  "devDependencies": {
    "nx": "17"
  }
}

... npm install && npx nx init installs Nx version 17.3.2 and succeeds with exit code 0.

Changing the specification to "nx": "18" installs Nx version 18.3.5 but npx nx init prints Checking dependencies and then hangs, apparently forever. I can use Ctrl-C to kill that process.

Changing the specification to "nx": "19" installs Nx version 19.6.1 and npx nx init prints:

npx nx init      

 NX   🐳 Nx initialization


 NX   📦 Installing dependencies


up to date, audited 115 packages in 290ms

22 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
✔ Would you like remote caching to make your build faster? · skip

 NX   🧐 Checking dependencies

... and then hangs forever. This cannot be cancelled with Ctrl-C, I have to run killall -9 node to stop it.

I'm afraid I don't know anymore if I'm reporting the same bug or a completely different bug, but perhaps you'll know more about what to make of this than I do.

[jaysoo]

@mechanical-fish Are there logs from .nx/cache/d/daemon.log?