Atom-script: node's command can't find

[mingyu0519]

Unable to run
node
Is it on your path?
PATH: /usr/bin:/bin:/usr/sbin:/sbin
execvp(): No such file or directory

[rgbkrk]

Run atom from the command line, not from the launcher. It needs your $PATH, which comes form your shell. Alternatively, use the run options command and set the explicit path to node.

[mingyu0519]

Problem solved, thank you

[harrisrobin]

Hey , the alternative option solves my problem however atom never remembers my node path, even if i run it from the command line. I think that hte reason behind this is that im not using bash but rather zsh but i don't know if that can be causing it.

Anyone knows why ? It's annoying to have to paste in the node path every time in run options.

Edit : @rgbkrk I looked over one of your solutions but i don't actually have a launchd.conf file and being a noob I don't really want to create it without knowing what im doing. What would you recommend here ?

Thanks !

[erran]

@HarrisRobin See this thread. I personally don't use bash either. I use fish and it has been working for me.

[rgbkrk]

Well, we could keep state of the options view we just don't have code for
it yet.

The atom achievements package has an (old) set of code that does
serialization if you want an example to implement it.

On Monday, August 18, 2014, Erran Carey [email protected] wrote:

@HarrisRobin https://github.com/HarrisRobin See this thread
https://github.com/rgbkrk/atom-script/issues/93#issuecomment-40860703.
I personally don't use _bash_ either. I use _fish_ and it has been
working for me.

—
Reply to this email directly or view it on GitHub
https://github.com/rgbkrk/atom-script/issues/181#issuecomment-52577727.

Kyle Kelley (@rgbkrk https://twitter.com/rgbkrk; http://lambdaops.com)

[mdeggies]

@HarrisRobin @erran
Did you guys ever figure out how to store & save the command path (without having to retype it every time?)

[rgbkrk]

@mdeggies Haven't had much time to work on this package other than some small fixes and PR merges. It's open to a contributor to look into.

[huangjihua]

Unable to run

babel-node
Did you start Atom from the command line?

atom .
Is it in your PATH?

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

[Kimilhee]

same problem with @huangjihua

[dengjonathan]

@huangjihua @Kimilhee Had the same problem- it's because you did not have the babel package installed in node. I think the updated atom-script uses Babel for ES6 support.

Below is what i did:

npm install -g babel-cli

[ArnoBuschmann]

Hm, same problem as @huangjihua @Kimilhee, I tried
npm install -g babel-cli
but it's not solving the issue. Any suggestions?

[Maxhodges]

babel cli docs discourage running globally

Note: Since it's generally a bad idea to run Babel globally you may want to uninstall the global copy by running npm uninstall --global babel-cli.

[ProVadimir]

Hello, i have problem with Atom!
help me, please!

[GuidoS]

I still don't understand the underlying issue that caused this problem and if you should not install babel globally, what is the solution?

[bmanandhar]

I am trying to run JavaScript program on 'atom' editor (not using command prompt) but having error : 'Unable to find command: node
Are you sure PATH is configured correctly?'
Where as Python program runs without issue.

Any suggestion, mine is desktop, Windows 7,
thanks