-
Notifications
You must be signed in to change notification settings - Fork 4
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 + node - after install receive "node\r no such file or directory" #2
Comments
Hm ... that's really strange. Is it happening with other modules installed globally? |
Nope - I have tons of globally installed modules and they all work fine....Grunt, serve, casper, phantom, etc. |
Hi, I think that your problem is identical to this one surjikal/sublime-coffee-compile#9 (I can't really test it because I'm a Linux/Windows user and don't have a Mac). Can you please read this tread surjikal/sublime-coffee-compile#9 and try changing your PATH. I'm referring this comment surjikal/sublime-coffee-compile#9 (comment) |
Hi, is the problem fixed. I too had the same error. I am working on ubuntu 13.04, node version 0.10.23. I think the problem is with setting the env to node. I could not fix the problem completely. One workaround is to execute the index.js auxilio is pointing to with node. In my case, it is
|
Because @askesian didn't post again here I was thinking that he found the problem. Personally I can't reproduce the problem. It seems that this problem is somehow related to the global PATH variable. The best thing which I could suggest for now is to make an alias which points to |
Have the same problem. VenkataHarish's solution worked for me |
I'm glad that @venkataharish's answer helped someone. |
MacOS Mountain Lion
Node 0.10.8 installed via nvm
Current console nvm node environment is 0.10.8
After installation:
Any ideas why this is happening? I also tried installing it without the -g flag, but because I'm using nvm to manage node, installing without the -g flag means I cannot access any installed package from the CLI.
The text was updated successfully, but these errors were encountered: