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
nvm use with nvmrc as node node v.0.0 (64-bit) is not installed. #388
Comments
I tried to throw in a standard version into the |
|
FYI, I created a workaround for this functionality by using the following commands in powershell: |
Any reason why this file isn't being used in Windows? It's super useful! |
The From a programming perspective, a shim is a nice theory to work with. Commands can be intercepted before the executable is called, making it possible to redirect commands to a different physical executable. Shims read the I've not added this to NVM4W mostly because it is symlink-based instead of shim-based. There is no preprocessing of node commands with a direct symlink. Furthermore, these tools are supposed to be node version managers, not developer environment managers. I do recognize the convenience of an nvmrc/node-version file, but I do not find the shim concept to be a truly viable option for all Windows users - especially those in stricter environments like corporate networks. The alternative is a hooks system. I opened this issue documenting the idea of using hooks. Hooks could achieve the same thing an As the JavaScript ecosystem has evolved, I still feel the core tenants of this project are viable for version management. However; I also feel there are better ways to manage JS runtimes (lessons learned from running this project since inception). I feel there are enough advances that it would be better to create a different project. So, I have no intention of adding this to NVM4W, but I do intend to address the need/desires in a different project. See the discussion where I discuss rt (runtime), the successor project I've been working on. |
first you should install node: |
My Environment
I'm using NVM4W version:
I have already...
My issue is related to (check only those which apply):
Expected Behavior
Running
nvm use
with an.nvmrc
withnode
in it should use the latest version of nodeActual Behavior
I see this instead
Steps to reproduce the problem:
.nvmrc
contentsrun
nvm use
The text was updated successfully, but these errors were encountered: