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

Running ember serve from Intellij IDE through Run (^R) throws errors - existing with code 127 #238

Open
rinoldsimon opened this issue Oct 22, 2018 · 5 comments

Comments

@rinoldsimon
Copy link

Description

/Users/workspace/web_ui/node_modules/.bin/ember serve
env: node: No such file or directory

Process finished with exit code 127

Steps to Reproduce

  • at times, after newly opening IntelliJ IDE
  • when i restart the IDE it works fine

Expected behavior: Start ember server

Actual behavior: Throws error in Run tool window

Reproduces how often: Alternate number of times.

Versions

  • IntelliJ:

IntelliJ IDEA 2018.2.5 (Ultimate Edition)
Build #IU-182.4892.20, built on October 16, 2018

  • The version of intellij-emberjs:

2018.2.4-0

@Turbo87
Copy link
Owner

Turbo87 commented Oct 22, 2018

it sounds like IntelliJ can't find your Node.js executable

@rinoldsimon
Copy link
Author

why does it happen at alternate number of time? However i specified node path under
preference -> languages & frameworks -> node.js and npm

@Turbo87
Copy link
Owner

Turbo87 commented Oct 22, 2018

why does it happen at alternate number of time?

I don't know...

However i specified node path under
preference -> languages & frameworks -> node.js and npm

I think we might not use that path but instead look for a global node binary. @makepanic might know this?

@makepanic
Copy link
Contributor

makepanic commented Oct 22, 2018

Yes we execute the node_modules/.bin/ember executable directly.
I guess on your system #!/usr/bin/env node returns nothing.

Maybe it's a good idea to also check if we can access the global node binary.

@rinoldsimon
Copy link
Author

I use nvm. So in my node interpreter my path will be ~/.nvm/versions/node/v8.9.4/bin/node.

As @Turbo87 mentioned that the addon doesn't use node interpreter path but instead it looks at node_modules/.bin/ember serve directly and this behaviour breaks sometimes and throws env: node: No such file or directory

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

3 participants