Skip to content
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

Yet another $PATH issue #50

Closed
joaocunha opened this issue Feb 13, 2015 · 4 comments
Closed

Yet another $PATH issue #50

joaocunha opened this issue Feb 13, 2015 · 4 comments

Comments

@joaocunha
Copy link

FIX: if you're using nvm, symlink your node binary folder with /usr/local/bin. In my case:

ln -s /Users/joaocunha/.nvm/v0.10.36/bin/node /usr/local/bin/node

Yosemite 10.10.2
nvm 0.23.3
node v0.10.36
Sublime Text 3 (stable 3065)

I tried all tricks I know to get node in my path, namely:

  • .zshrc
  • /etc/launchd.conf
  • /etc/paths.d
  • launchctl setenv PATH $PATH

...but I still get the error:
image

Maybe we could add "node-path" to the JSON config file so we can pass an arbitrary value? This is what CSSComb is doing.

@sindresorhus
Copy link
Owner

Where is your node binary located $ which node? On OS X GUI apps doesn't get the $PATH so I have to manually define it:

env['PATH'] += ':/usr/local/bin'

@joaocunha
Copy link
Author

@sindresorhus

joaocunha% $ which node
/Users/joaocunha/.nvm/v0.10.36/bin/node

I think a symlink would solve my issue, but making it configurable would be a good addition. I can PR that if you agree.

@sindresorhus
Copy link
Owner

I don't see the point in making it configurable when you can just symlink it. Symlinking it will fix it for all tools instead of having to have an option for all these tools.

@joaocunha
Copy link
Author

Agreed. I think a notice in the readme for nvm users would do some good, tho.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants