-
Notifications
You must be signed in to change notification settings - Fork 214
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NX console vscode extension is unable to reliably find projects in the current workspace #2302
Comments
Hi,
Thank you! |
Hi Max, This is what I have in the
And this is the output from
Wow I did not know I can debug like this. What do these errors mean? How can I increase the max listeners and what value should I set it to? Thanks for looking into this. |
Have the same issue. @soosap Do you know if there is any other ways to import a project e.g. manually? For me this is blocker as can not move forward to basically run the project. |
are you seeing the sane error while using the cli @viachmev ? |
The final solution for myself - switched node version form 20 to 22 and now everything works even on the latest nx version (20.3). |
In my case nx hang indefinitely (both console commands as well as the vscode extension) during project graph calculation once I added a second new app to my monorepo. After 2h of trying different things, I found out that even the individual apps need a package.json or else it will not work (even tho for single version strategies where the docs say you don't need it). |
Current Behavior
NX console has problems loading the projects in the current workspace. Every once in a while reloading the window does resolve the problem.
But then a day later or two it starts getting stuck in "We couldn't find any projects in this workspace." notice.
Expected Behavior
The projects should be loading and visible in the NX Console extension tab.
Steps to Reproduce
Install latest version on nx and nx-console extension and navigate to the extension tab.
Failure Logs / Images / Videos
The text was updated successfully, but these errors were encountered: