npm run build doesn't work on Windows

[Cleanshooter]

SET NODE_ENV=production & gulp release

[16:36:17] Using gulpfile ~\Documents\Projects\example-project\gulpfile.js
[16:36:17] Starting 'publish:tag'...
[16:36:17] Starting 'publish:npm'...
[16:36:17] Starting 'build:example:files'...
[16:36:17] Starting 'build:example:css'...
[16:36:17] Starting 'build:example:scripts'...
events.js:160
throw er; // Unhandled 'error' event
^

Error: spawn npm ENOENT
at exports._errnoException (util.js:1026:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:193:32)
at onErrorNT (internal/child_process.js:359:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickCallback (internal/process/next_tick.js:98:9)
at Module.runMain (module.js:606:11)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3

npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\Moto\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "release"
npm ERR! node v6.9.1
npm ERR! npm v4.0.2
npm ERR! code ELIFECYCLE
npm ERR! react-material-grid@0.0.5 release: SET NODE_ENV=production & gulp release
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-material-grid@0.0.5 release script 'SET NODE_ENV=production & gulp release'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the react-material-grid package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! SET NODE_ENV=production & gulp release
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs react-material-grid
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls react-material-grid
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Moto\Documents\Projects\example-project\npm-debug.log