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 unable to start in VS Code #1955
Comments
Hey! The good thing is, for workspaces > 16.4, we're getting rid of We're going to release a new version soon or you could build the master version from source today and try it! |
Oh, that is good news. What information exactly would be useful for you? Could you provide me with instructions on how to build the vsix myself locally? Here are some more specifics from my device settings.
|
It's really easy!
|
Thanks for the instructions @MaxKless. This worked. Am I doing something wrong? Nevertheless, I installed the self-built plugin in my environment and there are no errors at first. |
yes that version is hard coded, it doesn't matter :) |
I see. I checked the developer console. And once I saw an error that the Nx Console failed to initialized. This is the exact Error when I try to refresh:
|
Huh when I build from master and install via .vsix, refreshing works... Maybe you need to wait a moment until it becomes available as the application bootstraps? |
Having the same issue on NixOS. Is there an ETA for the next release? @MaxKless |
It seems like the Nx Console is failing to initialize. The above-mentioned error happens consistently.
An ETA for the next release would be appreciated. |
Hey! Sorry people are on vacation here already so the next release will be first week of Jan :) |
Update: The issue persists with v18.12.0. Hi @MaxKless. I see that a new Version 18.11.1 was released. Well done! The workspace is not detected. There is no Output available for the nx console. And a refresh throws an error message. There is also nothing in the Developer Tools. |
@clemenscodes check out this writeup that might fix your NixOs issue: #2051 @mrvonwyl are you sure you have the right VSCode installed for your windows version? As in x64 vs x32. It's a common mistake that often causes issues like this. |
@MaxKless Thanks for the heads up! Using the writeup I successfully solved this issue. :) |
@MaxKless yes. My VisualStudioCode.exe is 64 bit as well as my Windows. Here is a screenshot of the about screen of VS Code if that helps. |
Hey @mrvonwyl any updates on this? Can you double check whether you node is installed for the right architecture as well? It might cause an issue like this |
I just tried with the latest version, 18.18.0. I still have the same behavior. Yes, my node arch is x64 as well (checked with |
Please go through the Troubleshooting Steps here: https://nx.dev/troubleshooting/troubleshoot-nx-install-issues |
Current Behavior
I cannot start the NX console and therefore not connect it to my workspace and use any of the functionality.
There are a few errors displayed as notification and the output has issues as well.
This is probably a duplicate of #1891. But that one seemed stale.
Expected Behavior
I would expect the console to bring this dependecy with me, or tell me how to solve it.
Steps to Reproduce
I am not sure. It seems to be connected to the fact that the environment which I work in is running behind a firewall which blocks most of the internet traffic. I can install npm packages directly.
The console was installed through VSIX.
I think it would be reproducible, on a pristine system without internet and a new VS code installation. Then try to install the console through VSIX.
The solution is probably to manually install the watcher dependency on the system. But I would not know how this needs to be done, so Nx Console finds it.
Failure Logs / Images / Videos
This output is printed several times
Environment
The text was updated successfully, but these errors were encountered: