"JSCS: Node interpreter file is not found"

I have two development environments, one on Ubuntu 14 and one on Debian 8. On both I'm having this issue that seems to affect only JSCS (I have also ES6Lint, so no panic):

Going to "JSCS Settings...":

And, just for double checking:

As seen I use NVM, JSCS runs on shell, but stopped working altogether under WebStorm.

WebStorm 2017.1 EAP
Build #WS-171.3780.21, built on March 9, 2017
WebStorm EAP User
Expiration date: April 8, 2017
JRE: 1.8.0_112-release-736-b11 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 3.16.0-4-amd64

Any .idea what could be wrong?

10 comments
Comment actions Permalink

try starting Webstorm from terminal - does the problem persist?

1
Comment actions Permalink

I met this problem when upgraded to 171.3780.79.

Node.js 6.10.0, JSCS - 3.0.7.
The path to node.js is correct.

Running from terminal, JSCS plugin reinstallation, .idea directory removing did not help.

Downgrade to 2016.3.5 HELPED.

One can find old WS here:

https://confluence.jetbrains.com/display/WI/Previous+WebStorm+Releases

I reported the bug:

https://youtrack.jetbrains.com/issue/WEB-26057

If someone knows some workaround - welcome. 

1
Comment actions Permalink

Hi Elena, thanks for the tip. Indeed the JSCS issue doesn't happen if I run WS from the terminal. Something broken on Toolbox 1.2.2259? Or is there some workaround for Toolbox?

0
Comment actions Permalink

If the IDE is launched from Terminal, it inherits Terminal environment, so it sees your variables defined in .bashrc config. But this is not the case when the IDE is started from desktop - it sees environment variables configured in ~/.profile (login shell), but not in interactive shell configuration files then. Plus, NVM patches environment variables on terminal startup only.

As a workaround, make required variables available in a login shell (i.e. for Bash, move them from .bashrc to .bash_profile or .profile).

0
Comment actions Permalink

Having the same issue in Windows 10

 

0
Comment actions Permalink

Strange. Please make sure that node.exe is in your %PATH%. Note that you need to restart WebStorm after altering system environment variables

0
Comment actions Permalink

I have the same issue. Have had it for half a year or so.

NVM is configured via .bash_profile, and i do not use .bashrc.

---
Build #WS-171.3691.10, built on March 1, 2017
WebStorm EAP User
Expiration date: March 31, 2017
JRE: 1.8.0_112-release-724-b5 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.12.3

0
Comment actions Permalink

You are correct.  I switch between MAC and Windows.  That was the case.  It was pointing to the wrong NODE installation

 

0
Comment actions Permalink

Hi,

I have the same issue.

My specs are as follows;

Ubuntu 16.04.2LTS 
Nvm installed
Running from terminal.

0
Comment actions Permalink

I have the same issue.

PhpStorm 2017.1
Build #PS-171.3780.104, built on March 21, 2017
JRE: 1.8.0_112-release-736-b13 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.12.3

jscs 3.0.7

node 6.7.0 trough nvm.

0

Please sign in to leave a comment.