The -exec part is important, as the execution will fail with the following error: /usr/local/bin/node /usr/local/bin/nodemon server.jsĤ Oct 13:56:50 - to restart at any time, enter `rs`Ĥ Oct 13:56:50 - watching: /Users/foo/testĤ Oct 13:56:50 - starting `node server.js`Ĥ Oct 13:56:50 - exception in nodemon killing nodeĪt errnoException (child_process.js:980:11)Īt Process.ChildProcess._handle.onexit (child_process.js:771:34) This will instruct the node interpreter to execute the nodemon script using the following command line: node /usr/local/bin/nodemon -exec /usr/local/bin/node server.js.
#WEBSTORM TERMINAL NOT WORKING WINDOWS 10 INSTALL#
This will install nodemon globally on your machine. To install nodemon, use the following (if required, use sudo to run the installation with root privileges: npm install -g nodemon You should save the debug/run config to file so your teammates can also easily debug/run your nodejs app like you Then from Webstorm 's run/debug config, set Node parameters to be :path_to_project_dir/node_modules/.bin/nodemon You may NOT have nodemon exists from which nodemon command, then you should have it in your package.json ie nodemon be installed at :project_dir/node_modules/.bin/nodemon usr/local/bin/nodemon) under "Node Clark, thanks for confirming.
It looks like the workaround with -exec isn't necessary anymore, at least when using the newest version of nodemon and Webstorm 7 or 8.Īll you have to do is specify your path to nodemon by obtaining its path with running which nodemon in your console (e.g.
0 kommentar(er)
