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
doesn't work with .nvmrc #169
Comments
|
@coreybutler I am from the Disaster Accountability Project and we have some developers who use windows and can't take advantage of the |
@inunotaisho26 - Fundamentally, this project is focused on preparing Node as if it were installed the same way Node would be installed without a version manager. While this feature has been requested before, it is not something I have enough spare time to support. Due to the number of people who request general environment management solutions (beyond just .nvmrc), I am experimenting with ideas for a commercial environment management app to streamline these processes. The time requirements for supporting the community's large wish-list will require funding or sponsorship, so I'll probably lean on the infrastructure I've already built for Fenix. The catch: no ETA. That said, see the roadmap. The "free" solution I've proposed is a hook system, similar to git's |
@coreybutler So basically two different approaches to installing multiple versions of node right? |
Sort of. There are two different philosophies, but they're more about using Node than installing it. Philosophy 1: Native Use (Direct Process) Philosophy 2: Augmented Use (Subprocess) General version management requires some level of shimming in order to prevent actually uninstalling/reinstalling node every time you need to switch a version (which would take forever). NVM4W aligns with the first approach by using symlinks to shim the installation directory, as opposed to option 2, which shims the executable. As a result, you're always running the node.exe executable directly, instead of running it as a subprocess.. |
Small bump to this issue. Just ran into it. It can't seriously be that hard. Here's what to do if a version is not supplied to
In other words, without version number specified, There's not much more to it. |
I'm glad I'm not the only one having this issue... |
@thany @jeromemeichelbeck Feel free to fork the project and add this functionality yourself. I'll post a link here when it's ready. |
I simply run nvm use |
My Environment
I have already...
My issue is related to (check only those which apply):
Expected Behavior
Same result as
nvm use 4.4.4
Actual Behavior
Output:
node v (64-bit) is not installed.
Steps to reproduce the problem:
created an
.nvmrc
file with4.4.4
as the node version.go to command line and run
nvm use
in the same folder as the file.The text was updated successfully, but these errors were encountered: