Document method to return to system node

[jorgebucaran]

Document method to return to system node

[hildjj]

fnm rm (node -v) worked. Suggest this gets doc'd.

[jorgebucaran]

@hildjj @maparent The new version of this package will not have a rm command (at first), so the only way to get back to system node is to uninstall this package.

Is this something you do often? If so, I can work on a system or default alias to do just that.

[yegorius]

I have created a fork where you can revert to system node and which doesn't set node version globally. Basically, it doesn't use $fish_user_paths universal variable and only changes $PATH which only affects current fish session. Also, nvm unuse will reset the $PATH to its initial state.
https://github.com/yegorius/fish-nvm

[hildjj]

Candidly, I went back to zsh. However, I'm happy to talk through my use case.

I develop with a system-installed nodejs (via homebrew on OSX). I like that it stays up-to-date when I update the rest of my local stack. Periodically (usually when I get a CI failure on an older version of Node), I want to drop down to a given version, debug, then go back to the most recent version.

[jwhitmarsh]

Apologies if this is the wrong place for this, but I think it is linked - I would add that if you leave a directory with an .fnmrc the node version should switch back to system (assuming there isn't an .fnmrc in the new dir)

[maparent]

I tried removing (on mac) and it still uses the old binary that was copied in ~/.config/fnm/bin/node
Also it means if I go back and forth between system and specific version it must re-download. Not that enthusiastic about that solution.
As for selecting the previous version, it's the fnm copy of my system node, which may not be the system node. (For one thing, the latter gets updated semi-automatically.)
So I'd really appreciate a fnm system command.

[jorgebucaran]

@jwhitmarsh It should be possible using your own node wrapper function.

See also:

• #75
• rewrite branch
• #39 (comment)