-
Notifications
You must be signed in to change notification settings - Fork 2
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
Document how it works #3
Comments
@luxferresum In brief, The
See install.sh and install.ps1 for more details. Thanks for your suggestion. Any idea or pull request is welcome. |
Thanks for clarification. I just realised that |
@luxferresum Do you mean manual installation? Just do the following steps:
The install script just did these things. It will detect the default shell, then add PATH to it. For now only Maybe we should add a section in README for users who use other shell like |
Thanks! Yes, documentation for manual installation would be nice. And no, my question was about shell-specific or local node versions. |
It's an interesting point. Seems they dynamically change Seems Nodenv's shims is a reasonable resolution. We'll investigate pros and cons of using such a mechanism |
nvm
can be quite annoying because it hooks deep into the shell. I've used nodenv so far on *nix, and I really like how transparent the functionality is.The usage of shims means I dont need any setup code that slows down my shell boot, or any hooks into my shell. I just need to
nodenv rehash
when I install a new global binary the first time. This especially also makes it compatible with exotic shells like fish.I would love if
nn
could become a unified solution that would also work on windows (the one think I dont have withnodenv
).However for now its very unclear how
nn
handles switching global binaries. Does it manipulate thePATH
or does it use something like shims?The text was updated successfully, but these errors were encountered: