Nx console plugin for Webstorm not considering NX_DAEMON_SOCKET_DIR

[MarcusElevait]

Nx console plugin for Webstorm not considering NX_DAEMON_SOCKET_DIR

[MaxKless]

Hey @MarcusElevait thanks for the report.
Are you setting the NX_DAEMON_SOCKET_DIR directly in the terminal?
If yes, there's no way for Nx Console to know what this inline env variable is set to. You should use a root .env file to set the env variable in a way that Nx Console can pick up as well. https://nx.dev/recipes/tips-n-tricks/define-environment-variables

Can you confirm that this issue persists even if you define it in this way?

[MarcusElevait]

Yes the issue still persists. And it was again pretty clear, that as soon as i deactivate the nx console plugin the issue is not there anymore.
Here is again the beginning of the daemon.log file:
[NX Daemon Server] - 2024-05-13T12:11:09.750Z - Started listening on: /home/marcus/Projects/aicosy/.nx/d.sock [NX Daemon Server] - 2024-05-13T12:11:09.753Z - [WATCHER]: Subscribed to changes within: /home/marcus/Projects/aicosy (native) [NX Daemon Server] - 2024-05-13T12:11:09.758Z - Established a connection. Number of open connections: 1 [NX Daemon Server] - 2024-05-13T12:11:09.760Z - Closed a connection. Number of open connections: 0 [NX Daemon Server] - 2024-05-13T12:11:19.609Z - [WATCHER]: package-lock.json was modified [NX Daemon Server] - 2024-05-13T12:11:19.609Z - [WATCHER]: Processing file changes in outputs [NX Daemon Server] - 2024-05-13T12:11:19.745Z - [REQUEST]: Updated workspace context based on watched changes, recomputing project graph... [NX Daemon Server] - 2024-05-13T12:11:19.745Z - [REQUEST]: package-lock.json [NX Daemon Server] - 2024-05-13T12:11:19.745Z - [REQUEST]: [NX Daemon Server] - 2024-05-13T12:11:20.324Z - Time taken for 'Load Nx Plugin: /home/marcus/Projects/aicosy/node_modules/nx/src/plugins/project-json/build-nodes/package-json-next-to-project-json' 28.765384000000267ms [NX Daemon Server] - 2024-05-13T12:11:20.694Z - Started listening on: /tmp/c3fb6aaef5aa7fc7fef2/d.sock

And i haven't done much. I've just run nx daemon --stop and then nx daemon --start and run npm i and that's it.

[MaxKless]

Thanks for confirming @MarcusElevait!
I was able to repro this and have a PR open to fix it in the nx repo. It requires some changes to environment variable loading so I sadly can't fix it from the console side. You'll have to migrate to the latest Nx version once it's merged & released.
Keep your eyes on this issue if you want to track its progress
nrwl/nx#23348

[MarcusElevait]

Thank you very much :-)

[MarcusElevait]

Is this fix already provided in the version v18.21.4 of the vs code plugin? Because we have seen this issue again

[MaxKless]

Hey! Yes this fix is provided in Nx but there was a revert in the latest Nx version.
I will release another Nx Console version with a fix ASAP. Thank you for your patience.

[MarcusElevait]

Thank you :-)

[MaxKless]

hey just letting you know, the new version is published and available. It should fix your issues, please let me know if it works.