-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Using the system node as default #1238
Comments
It sounds like you're saying having |
That's right. Both exec and run are failing. Other things seem to work alright, though I haven't tested much of yet but will be doing so. Btw what exactly is the 'default' node, is it what's used anytime you're not in a directory with an .nvmrc? And sometimes I see people aliasing things to |
In If you don't use an |
With regards to npm run/exec not working with system, is there any workaround I can use now that would let me access the system node while I'm in a folder with an .nvmrc, without having to leave that folder first? For example if I do Btw here is my output of
|
You can always |
nvm alias default system Is this what you want? |
I've done
nvm alias default system
, and doingnvm use system
showsNow using system version of node: v6.5.0 (npm v3.10.6)
. But if I donvm exec system node app.js
I get an error:What's the correct way to use the system node as the default? (I only switch to nvm versions of node when I'm in a directory with an .nvmrc.)
The text was updated successfully, but these errors were encountered: