Some npm scripts fail in windows

[aerze]

Some of the build scripts return errors.

npm run assets
npm run entities
npm run scenes

$ npm run assets

> ox2d@0.2.1 assets c:\Users\aerze\projects\ox
> ./src/tools/assetsWatcher.js

'.' is not recognized as an internal or external command,
operable program or batch file.

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "c:\\Program Files\\nodejs\\node.exe" "c:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "assets"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE
npm ERR! ox2d@0.2.1 assets: `./src/tools/assetsWatcher.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the ox2d@0.2.1 assets script './src/tools/assetsWatcher.js'.
npm ERR! This is most likely a problem with the ox2d package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ./src/tools/assetsWatcher.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls ox2d
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR!     c:\Users\aerze\projects\ox\npm-debug.log

Simple solution, I think, is to just but node in front of the string. windows doesn't read the hash bang and the top of the files.

{
        "assets": "node ./src/tools/assetsWatcher.js",
        "entities": "node ./src/tools/entitiesWatcher.js",
        "scenes": "node ./src/tools/scenesWatcher.js"
}