Feature Request: Automatically add the current default nodejs version to the PATH variable in windows.

[spa5k]

Although we can simply add fnm execution script into the powershell, but since its not available in the path directory, we can not use it during other process, for example, git bash, git hooks. And have to do weird hooks in order to make fnm work there.

I don't think it will be that difficult to add both fnm, the current default node js version and default npm version into the path.

https://github.com/coreybutler/nvm-windows/blob/5803c4f8c7766c670996fbce3fc113a9b0d95050/src/nvm.go#L516

The nvm-windows is trying to do something like that here.

[dornfeder]

I had a similar problem, especially with the Git Hooks. My solution for this was to add the symlink folder for the default alias to the PATH environment variable in Windows:

C:\Users\my-username\.fnm\aliases\default

That way, in an environment where fnm is not set up, like git hooks , or git bash in your case, the default node and npm versions are available. And when fnm is set up, it will override the PATH according to the fnm setup.

You can do this with any alias you like, of course. Doesnt have to be the default.

Hope this helps.

[spa5k]

I can do that, but my point was to make it a automatic feature into the FNM, i should have rephrased my sentence.

[dornfeder]

I can do that, but my point was to make it a automatic feature into the FNM, i should have rephrased my sentence.

Sure that would be nice to have, but in the meantime i just wanted to leave this workaround here so that people with similar problems don't have to struggle as much as I did. :)

[JohyC]

this Feature Request is good idea!
in now I can`t use node in systemctl;
i need this feature ...

[BryanAdamss]

get same problem in Git hooks

.git/hooks/pre-commit: line 14: node: command not found

[segevfiner]

This will be a problem for any GUI application that ends up invoking Node.js and is not started from a shell with fnm activated, e.g. Visual Studio. Would be cool to have a way to handle that cleanly...

[Schniz]

friendly reminder than in scripts you can do fnm exec --using="version of choice" [your command here]

i have ideas on how to solve that. would not solve all issues, but node etc will certainly work. but... no time: i have family, work, and other side projects.

if one of you have ideas on how to solve this and can put some effort and time (after describing their idea and getting approved) it would be lovely

[segevfiner]

Tried that. But I hit #1054. And in my case this is some command embedded inside some other project which needs to work for users who install Node.js in other ways.