Nx Console is empty #1197
Comments
|
Does the error still happen when you open https://GitHub.com/nrwl/nx-examples? Also can I get the contents of your package.json please |
|
@Cammisuli I also have the same error :/
Installed Extension version |
|
I think that bug was introduced in version |
|
A few folks are having the issue but I can't reproduce it with any repo I have Does everything work well with the nx-examples repo? |
|
potentially fixed with #1199 where it will release as 17.13.2 |
I had the same problem, and downgrading solved the issue. Thanks for the advice @stepanic |
|
Can everyone try the latest version |
|
Tried with 17.13.2, still doesn't work. I am using two environments - windows filesystem & wsl2. For windows filesystem everything works as expected, for wsl2 it doesn't. Reverting to version before 17.13.x "fixes" the issue. None of the versions 17.13.x work. |
|
Update: Tried provided nx-examples and that one works. So tried to copy non-functional repos to windows filesystem and also does not work there O.o. After comparing why some repos work and some not, I came to conclusion, that problem may be when trying to open monorepos. So tried to open non functional project in wsl2 in such a way that angular.json is in the root and it did work. So probably problem is when opening monorepos? |
|
I can confirm, 17.13.2 didn't help, it breaks down again (after upgrading from 17.12.4) |
|
So is everyone opening sub folders from the main workspace? |
|
@miskith Do you have an example of a repo that you're experiencing the issue with? Or exact instructions on how you're reproducing it? |
|
@Cammisuli Sorry, can't provide you with repo as those are private projects. But basically this command should do the magic (tested it for me on Windows and WSL2, for both broken): |
|
@miskith opening in a directory above worked before? 😮 |
|
If that's the case can you then just select the child workspace with this item? Nx Console always searched in parent directories by default to find a workspace. If a workspace isn't in the parent directories, the menu item I mention should help with setting the correct child workspace. Then if you reopen the same directory in VSCode, it should remember your last manually selected workspace. |
|
AHH! I know what could be the issue now... We have these activationEvents triggers: nx-console/apps/vscode/src/package.json Lines 39 to 44 in c8c808e But I don't believe onView:nx-console works for non-built-in views. I can change that to onStartupFinished so the extension always activates.
|
|
Yes, as I said, after reverting to version before 17.13.x , it worked well. Changing workspace doesnt work the whole nx window is empty (sorry, just noticed my issue is a bit different than original issue as @ecohanim sees at least something in the window). This is how it looks for me with new version: |
|
Let's try again with |
|
Cool, so can't speak for others, but for me 17.3.3 fixed it. I had to load correct workspace through "Change workspace" button, but that is fine, at least it works :). And after VS Code restart it remembers the previously set workspace, just as you said. |
|
Ok I'll wait for others to speak up before closing this issue. |
|
I can confirm 17.3.3 now works, but only after I manually selected the Workspace. 17.2.x would do that automatically. ...and thank you for a wonderful service BTW
|
|
still not working for me, having the below error
and change workspace button doesn't help in my case |
|
@ecohanim im not sure if you did this already, but can I get the contents of your package.json file? |
not sure i can publish it. is there something specific you need from that file? |
|
Just the dependencies and devDependencies |
sorry, i cant publish that file |
|
17.12.x works for us but not anything over 17.13.x (including 17.13.3) We haven't done our yearly upgrade cycle yet so we're still on v10. Haven't had any issue with console previously. "dependencies": {
|
|
I also have the same issue in my WSL2 environment. In the output window i get this message:
|
|
Thank you @kyleryanbanks! I was able to reproduce it with your dependencies. I pushed up a PR with a fix. Hopefully that fixes it up for everyone 😓 |
|
For everyone else, |
having new error now after updating to the latest version
|
|
@ecohanim its hard to debug yours because I can't reproduce your use case. I'd either need the dependencies of your package.json or a reproduction in another repo 🙁 |
|
I just installed v17.13.4 and get this error: Output of:
Node : 14.17.0 nx : 12.10.0 |
|
@Cammisuli I tried 17.13.4 and I'm getting the same issue as @ecohanim. This is actually getting output now at least, before is was just the empty {}. Everything seems to load fine until it tries to load the projects. We're still back on the pre-workspace config v10 at the moment, so I assume it's just not loading from the right config? |
|
That could be it. I just installed the dependencies that was mentioned earlier in the nx examples repo and saw the issue you first mentioned. I'll try again with a fresh v10 workspace with |
|
Can you all try |
|
Hey @Cammisuli, that last fix seems to have gotten it running again for us. Thanks for all the help. |
|
seem to be working at my env as well :) |
|
Yay! Thanks everyone for your patience in getting this fixed. Now I'm going to go on vacation 😪😮💨 |
|
We updated this morning and can see the projects but have no expandability. |
|
Just adding information, projects expand fine for us on the .5 update. |
|
@labeled can you create a new issue with your workspace info ( |
|
@labeled I actually found out what could be the issue and I'm going to release a new version soon. |
@Cammisuli If you would like I could pull down your branch and test locally before you commit to master. |
|
@labeled yup, that's what I found in one of the repos I had. I thought that standalone config were introduced with Nx 13, but they were there for 12. So I just had to change the minimum version to be less than 12, instead of less than 13 to use just regular old read json. If |
|
That resolved it! Much appreciated sir :) |
|
I have the same issue - nx console empty with |
|
That looks like a typical VSCode error. If you hard close vscode and reopen it, it should be fixed. If not, please make a new issue. |
|
Hello, people .. |
i am using nx console on vscode, it stopped working recently after the recent changes of using nx tools to parse nx.json
my vscode is installed on windows 10 and my project is on wsl2
everything was working fine till the recent updates of nx console
see image below for the error i am getting on the output tab as well as the error popup window on the bottom right
The text was updated successfully, but these errors were encountered: