Error: spawn UNKNOWN when running Sails

I'm following this and this tutorial (they are essentially the same) to get Sails to run under Webstorm but it refuses to work. If I run app from command line with "sails lift" it works. If I edit package.json like this:

"scripts": {
"start": "node node_modules\\sails\\bin\\sails.js lift"

and create NPM configuration, it also starts up normally. But Node.js configuration described in tutorials doesn't work, every time I start the app, at stops with this error:

throw errnoException(err, 'spawn');
Error: spawn UNKNOWN
at exports._errnoException (util.js:856:11)
at ChildProcess.spawn (internal/child_process.js:298:11)
at exports.spawn (child_process.js:362:9)
at Object.exports.fork (child_process.js:54:10)
at Hook.runTask (i:\Users\Dread\Documents\GitHub\porocila-treningov\node_modules\sails\lib\hooks\grunt\index.js:54:32)
at Hook.bound [as runTask] (i:\Users\Dread\Documents\GitHub\porocila-treningov\node_modules\lodash\dist\lodash.js:729:21)
at Hook.initialize (i:\Users\Dread\Documents\GitHub\porocila-treningov\node_modules\sails\lib\hooks\grunt\index.js:29:12)
at Hook.bound [as initialize] (i:\Users\Dread\Documents\GitHub\porocila-treningov\node_modules\lodash\dist\lodash.js:729:21)
at i:\Users\Dread\Documents\GitHub\porocila-treningov\node_modules\sails\lib\hooks\index.js:74:14
at i:\Users\Dread\Documents\GitHub\porocila-treningov\node_modules\async\lib\async.js:451:17
at i:\Users\Dread\Documents\GitHub\porocila-treningov\node_modules\async\lib\async.js:441:17
at _each (i:\Users\Dread\Documents\GitHub\porocila-treningov\node_modules\async\lib\async.js:46:13)
at Immediate.taskComplete (i:\Users\Dread\Documents\GitHub\porocila-treningov\node_modules\async\lib\async.js:440:13)
at processImmediate [as _immediateCallback] (timers.js:383:17)

I'm using Webstorm 11.0.3, Node 5.5.0 and Windows 10.

1 comment
Comment actions Permalink

configuration like works fine for me (and actually is is exactly the same as "start": "node node_modules\\sails\\bin\\sails.js lift" used by you).

The error you get is not too verbose - it just means that spawning child process has failed for unknown reason. Things to check:

  • does the same command work when running from system console?
  • what Node.js version do you use?
  • do you have 'Include parent environment variables' enabled in your Node.js run configuration? Open 'Environment variables' dialog using ellipsis button in Environment field to check it

Please sign in to leave a comment.