-
Notifications
You must be signed in to change notification settings - Fork 142
Error: Unable to execute npm get prefix. Please make sure Atom is getting $PATH correctly #408
Comments
Open a terminal and do
paste the value into settings |
If you are not using global node and eslint, then uncheck the |
Thank you @steelbrain, the |
This error popped up for me today too. |
Did the comments earlier in the issue resolve it for you @OKNoah, or are you still running into problems? |
@thearabbit You have selected |
So I need install vai |
By checking global eslint, you declare that you have eslint and therefore node installed globally, to get the prefix path of your node installation you should do |
Sorry it have problem with |
That is not actually an error but a user misconfiguration, please configure eslint to allow es6+ syntax |
Could you help me, how to solve? |
I personally use babel-eslint as my parser, check it out here https://github.com/babel/babel-eslint#setup |
Now I tried to install |
npm install -g eslint
apm install language-babel |
@thearabbit This is a bug report for a completely different thing, I would love to help you but you're asking for help about something very basic of eslint (not related to this Atom package), I would recommend you google some |
Very thanks for your helping, I will try the best. |
@steelbrain if you are using global node, but local eslint how should you configure things? |
@annacollins85 You shouldn't have to configure anything, it should run out of the box in that scenario :) Also this is a pretty old issue, if you're still having this problem, please open a new issue instead |
Hi,
After today's update I've started getting this message every time I open a JS file:
The text was updated successfully, but these errors were encountered: