Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Commands in package.json broke windows compatibility

See original GitHub issue

npm ERR! Windows_NT 10.0.10240
npm ERR! argv "C:\\tools\\nodejs\\node.exe" "C:\\Users\\...\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v4.0.0
npm ERR! npm  v3.3.3
npm ERR! code ELIFECYCLE
npm ERR! @este/universal@ preinstall: `(cd web && npm link ../common) && (cd native && npm link ../common)`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @este/universal@ preinstall script '(cd web && npm link ../common) && (cd native && npm link ../common)'.

Issue Analytics

State:
Created 8 years ago
Comments:22 (15 by maintainers)

Top GitHub Comments

2reactions

solcikcommented, Sep 20, 2015

Exactly these commands are problem.

C:\Users\...\www\_JS\este [master]> (cd web && npm link ../common)
At line:1 char:9
+ (cd web && npm link ../common)
+         ~~
The token '&&' is not a valid statement separator in this version.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : InvalidEndOfLine

“Windows (powershell) way”…

C:\Users\...\www\_JS\este [master]> cd web; npm link ../common
C:\Users\...\AppData\Roaming\npm\node_modules\@este\common -> C:\Users\...\www\_JS\este\common
C:\Users\...\www\_JS\este\web\node_modules\@este\common -> C:\Users\...\AppData\Roaming\npm\node_modules\@este\common -> C:\Users\...\www\_JS\este\common

1reaction

steidacommented, Sep 22, 2015

@grabbou And now you see why I prefer Gulp - because Node.js ensures scripting is cross platform. Npm script are ok unless they are just aliases imho.