Window script error running npm start validate

[comfroels]

Running npm start validate after an npm install on windows gives me the following error:

Script: C:[path_to_code]\package-scripts.js
Line: 2
Char: 1
Error: Syntax error
Code: 800A03EA
Source: Microsoft JScript compilation error

This is on Node v 6.1.0
and NPM v 3.8.6

Which the error is just on the keyword const so, not knowing about es6, possibly? But I verified I'm running Node 6

[comfroels]

Npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start',
1 verbose cli   'validate' ]
2 info using npm@3.8.6
3 info using node@v6.1.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle javascriptair.com@1.0.0~prestart: javascriptair.com@1.0.0
6 silly lifecycle javascriptair.com@1.0.0~prestart: no script for prestart, continuing
7 info lifecycle javascriptair.com@1.0.0~start: javascriptair.com@1.0.0
8 verbose lifecycle javascriptair.com@1.0.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle javascriptair.com@1.0.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\nathan.white\Documents\Codez\site\node_modules\.bin;C:\Program Files\nodejs;C:\ProgramData\Oracle\Java\javapath;C:\tools\ruby22\bin;C:\windows\system32;C:\windows;C:\windows\System32\Wbem;C:\windows\System32\WindowsPowerShell\v1.0\;C:\HashiCorp\Vagrant\bin;C:\ProgramData\chocolatey\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files\nodejs\;C:\Ruby22\bin;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\nathan.white\AppData\Local\Programs\Git\cmd;C:\Users\nathan.white\AppData\Local\Programs\Git\mingw64\bin;C:\Users\nathan.white\AppData\Local\Programs\Git\usr\bin;C:\Users\nathan.white\AppData\Local\atom\bin;C:\Users\nathan.white\AppData\Roaming\npm
10 verbose lifecycle javascriptair.com@1.0.0~start: CWD: C:\Users\nathan.white\Documents\Codez\site
11 silly lifecycle javascriptair.com@1.0.0~start: Args: [ '/d /s /c', 'package-scripts "validate"' ]
12 silly lifecycle javascriptair.com@1.0.0~start: Returned: code: 1  signal: null
13 info lifecycle javascriptair.com@1.0.0~start: Failed to exec start script
14 verbose stack Error: javascriptair.com@1.0.0 start: `package-scripts "validate"`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:239:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:850:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid javascriptair.com@1.0.0
16 verbose cwd C:\Users\nathan.white\Documents\Codez\site
17 error Windows_NT 10.0.10586
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start" "validate"
19 error node v6.1.0
20 error npm  v3.8.6
21 error code ELIFECYCLE
22 error javascriptair.com@1.0.0 start: `package-scripts "validate"`
22 error Exit status 1
23 error Failed at the javascriptair.com@1.0.0 start script 'package-scripts "validate"'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the javascriptair.com package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     package-scripts "validate"
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs javascriptair.com
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls javascriptair.com
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

[comfroels]

The error comes in a pop up and is delivered by Windows Script Host, if that helps

[comfroels]

So read some things about Windows Script host, and tried to change all .js extensions to default to Node. The pop up doesn't appear anymore, but it doesn't appear to actually do anything. Just logs out what I'm running and pops me back to the cli

[kentcdodds]

Ah, so you're using WSH rather than the command line? Yeah, I'm not sure what to tell you other than try to use the command line. Bash is preferable, but it should work in a normal windows command prompt as well.

[comfroels]

I'm running it through the command line, I'm just getting a popup from the WSH. I'll try it from a git bash prompt though... and see if that helps

[kentcdodds]

I'm not familiar with windows development, but I believe there have been contributions from some other windows users. If you find what's wrong, I'd really appreciate a PR to fix it. Thanks!

[comfroels]

I'll try this out on a different Windows machine later tonight... if that doesn't work: I will boot up my linux box. Thanks for the help @kentcdodds

[comfroels]

Okay, so I went home to my other computer, and still got the same error. However, I figured out how to get windows to execute the package-scripts though... by adding .cmd to the end of package-scripts. Don't know how we can change it so that it works xplat, ideas anyone?

[kentcdodds]

by adding .cmd to the end of package-scripts.

Do you mean you change package-scripts.js to package-scripts.js.cmd? Or do you change the "start": "package-scripts" in the package.json to be "start": "package-scripts.cmd"?

What if we did: "start": "node package-scripts"? Would that work?

I'd prefer to update p-s to work with windows out of the box, so if there's anything we can do to make that happen that'd be great. Not sure why it's not working for you though. I'm doing the same thing for p-s as other packages...

[comfroels]

Hmm. Alright.
Yeah I mean in the "start": "package-scripts" in the package.json. Changing to "start": "package-scripts.cmd" works. Yeah I tried the "start": "node package-scripts" and that seems to start running but it doesn't actually execute anything (it prevents the error but doesn't actually build)

[kentcdodds]

This is really odd... Do you mind reaching out to our overlords at Stack Overflow and seeing if there's a solution to this problem?

[comfroels]

Contacting the overlords....
👑

[KrisSiegel]

If you want something that runs universally on Windows and nix you should execute the JavaScript file as "start": "node package-scripts.js"

If you simply do "start": "package-scripts" then it is run as it package-scripts is an executable which in this case it is not (granted you can set defaults on your system to have node handle JavaScript but that required setup external to your project).

[kentcdodds]

Interesting! Thanks @KrisSiegel! Could you give that a try @comfroels?

Do you know how packages like gulp or webpack accomplish this? I've never had someone from windows say that I need to change my scripts to be node gulp.js or node webpack.js...

[comfroels]

After doing the change from @KrisSiegel it gives me this output,

> javascriptair.com@1.0.0 start C:\Users\nathan.white\Documents\Codez\site
> node package-scripts.js "validate"

and throws me back to the prompt, doesn't seem to actually execute anything.
@kentcdodds package-scripts is meant to be executed at that point right? pretty much as an executable? I feel like that's why the package-scripts.cmd works.. (However it ends up erroring out on the npm start validate saying that '.' is not a recognized command. But I can get npm start server to work 100%)