@WebStormIDE Removing this entry (manually) from the "PropertiesComponent" component section in the workspace.xml file fixed the problem: <property name="nodejs_interpreter_path" value="$USER_HOME$/.nvm/versions/node/v6.11.1/bin/node" /> Probably because debug config is 10.4.
The option in PropertiesComponent states what Node.js version is selected in the project settings. Run/Debug configuration can use any Node.js version and it would be stated in RunManager - configuration. So there shouldn't be any problems because of that.
-
-
So far we can't reproduce the problem, sorry.
-
Ok, thanks anyway. I know what to do if it happens again. Just delete that entry.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.