NPM Lifecyle Error on Windows 10

Hello! I get the following error (or a version of this) running any of the npm commands (eg. npm run start)

$ npm run start

> mikeworks-sql@0.0.0 start C:\Users\cassi.gs\Sites\Personal\NEW-SQL\sql
> scripty

Executing "C:\Users\cassi.gs\Sites\Personal\NEW-SQL\sql\scripts\start.sh":

> #!/usr/bin/env sh
> node dist/index.js
>


internal/child_process.js:323
    throw errnoException(err, 'spawn');
    ^

Error: spawn UNKNOWN
    at _errnoException (util.js:1022:11)
    at ChildProcess.spawn (internal/child_process.js:323:11)
    at exports.spawn (child_process.js:502:9)
    at module.exports (C:\Users\cassi.gs\Sites\Personal\NEW-SQL\sql\node_modules\scripty\lib\run\spawn-script.js:8:15)
    at C:\Users\cassi.gs\Sites\Personal\NEW-SQL\sql\node_modules\scripty\lib\run\commandify.js:6:7
    at C:\Users\cassi.gs\Sites\Personal\NEW-SQL\sql\node_modules\scripty\node_modules\async\lib\async.js:718:13
    at iterate (C:\Users\cassi.gs\Sites\Personal\NEW-SQL\sql\node_modules\scripty\node_modules\async\lib\async.js:262:13)
    at async.forEachOfSeries.async.eachOfSeries (C:\Users\cassi.gs\Sites\Personal\NEW-SQL\sql\node_modules\scripty\node_modules\async\lib\async.js:281:9)
    at _parallel (C:\Users\cassi.gs\Sites\Personal\NEW-SQL\sql\node_modules\scripty\node_modules\async\lib\async.js:717:9)
    at async.series (C:\Users\cassi.gs\Sites\Personal\NEW-SQL\sql\node_modules\scripty\node_modules\async\lib\async.js:739:9)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mikeworks-sql@0.0.0 start: `scripty`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mikeworks-sql@0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\cassi.gs\AppData\Roaming\npm-cache\_logs\2018-04-26T23_58_04_436Z-debug.log

After some digging it I could get the commands to run using the windows suggestion from Scripty

In order to add Windows support, you could define scripts-win/test/unit.cmd with this script:

@ECHO OFF

teenytest --helper test\unit-helper.js "lib\**\*.test.js"

Oddly enough I have Cygwin installed and can run the script manually (eg. $ bash scripts/start.sh), but I can’t run the npm commands without the script-win file.

[Dissolving-in-Eternity]

npm install didn’t work - the same errors as before. But I tried npm i winston@next --save for manual winston update and it worked. Now the project is up and running on localhost. 😃 Thanks for your help!

Still confused about typescript errors though.

[mike-north]

@Dissolving-in-Eternity the short answer is – TypeScript makes breaking changes all the time, and I haven’t had a chance to keep up with the latest release. Thankfully, it shouldn’t get in the way of your learning experience.

Good luck with the course!