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

How do I set a custom node path? #60

Closed
petercunha opened this issue Jan 25, 2017 · 12 comments
Closed

How do I set a custom node path? #60

petercunha opened this issue Jan 25, 2017 · 12 comments

Comments

@petercunha
Copy link

@petercunha petercunha commented Jan 25, 2017

I'm getting an error when ever I try to use a utility from the Tools --> NodeJS menu:

Node binary could not be found in PATH

Consider using the node_command setting for the Node plugin

PATH is: /usr/bin:/bin:/usr/sbin:/sbin

I ran which node in terminal and got /usr/local/bin/node. How do I set that as the default node path?

@techaware
Copy link

@techaware techaware commented Jan 31, 2017

I am also facing the same issue.

@varp
Copy link
Collaborator

@varp varp commented Feb 5, 2017

@petercunha @techaware You can set the default node path either by Preferences --> Package Settings --> NodeJs --> User Settings or add /usr/local/bin to your PATH

@eselkin
Copy link

@eselkin eselkin commented Feb 18, 2017

As Packages/User/Nodejs.sublime-settings
{
"node_command": "/usr/local/bin/node",
"node_path": "/usr/local/bin/node",
"node" : "/usr/local/bin/node"
}
Using this setting or any of those individually do not work.
Nor does setting path in Preferences.sublime-settings

@JethroSovr
Copy link

@JethroSovr JethroSovr commented Feb 24, 2017

I used brew to install the NodeJs
type "where node" in terminal,
it showed "/usr/local/bin/node"
so I also got this problem ,
I try to setting like eselkin by edit "Nodejs.sublime-settings"
but it doesnt work.
So my fix like this:
edit the "Nodejs.sublime-build"
"osx":
{
"cmd": ["killall node;/usr/local/bin/node $file"]
}
use "/usr/local/bin/node" to replace "node"
now it worked, but I think it must have the another way to fix it.

@varp
Copy link
Collaborator

@varp varp commented Feb 24, 2017

I'm digging the issue. Will give feedback asap

@natanavra
Copy link

@natanavra natanavra commented Apr 28, 2017

Any news on this one?

@varp
Copy link
Collaborator

@varp varp commented Apr 29, 2017

@natanavra till May, 2 I will give a feedback

varp added a commit that referenced this issue Apr 30, 2017
@varp
Copy link
Collaborator

@varp varp commented May 1, 2017

@petercunha @techaware @eselkin @JethroSovr @natanavra please install plugin from the branch issue-60 to check if the issue is resolved. I'll be waiting for feedback to merge in master branch and release a new sublime package

@eselkin
Copy link

@eselkin eselkin commented May 1, 2017

Seems like it runs, but there is no output on the run. I do see its process running after using the run menu item.

@varp
Copy link
Collaborator

@varp varp commented May 2, 2017

@eselkin I've heard you. I'll be working on this and will give you feedback. As always in couple of days...

@varp
Copy link
Collaborator

@varp varp commented May 13, 2017

Fixed in a new release v1.5.5. Check out the master branch or install the new version from package manager.

@varp varp closed this May 13, 2017
@MadCowWeb
Copy link

@MadCowWeb MadCowWeb commented Oct 17, 2019

I used HomeBrew and found mine here:
/Users/yourname/.nvm/versions/node/v10.16.3/bin/node

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

Successfully merging a pull request may close this issue.

None yet
7 participants