Open milahu opened 3 years ago
remove scrambled output from npm install
npm install
progress is enabled by default instead of --no-progress, we could also use npm config set progress=false
--no-progress
npm config set progress=false
for debugging, we could use --verbose or npm config set verbose=true but this is too verbose for normal use
--verbose
npm config set verbose=true
the root cause for the scrambled output is probably a buffer issue so that \r is parsed wrong
\r
before
> aws4@1.11.0 preinstall /build/node_modules/aws4 > /build/node_modules/.hooks/preinstall ......] \ postinstall:readable-stream: info lifecycle readable-str0m > @nodegui/nodegui@0.30.2 postinstall /build/node_modules/@nodegui/nodegui > cross-env npm run setupqt && (node ./scripts/skip.js || npm run build:addon) sh: /build/node_modules/.bin/cross-env: /usr/bin/env: bad interpreter: No such file or directory npm ERR! code ELIFECYCLEifecycle @nodegui/nodegui@0.30.2~post[0m npm ERR! errno 126
after
> aws4@1.11.0 preinstall /build/node_modules/aws4 > /build/node_modules/.hooks/preinstall > @nodegui/nodegui@0.30.2 postinstall /build/node_modules/@nodegui/nodegui > cross-env npm run setupqt && (node ./scripts/skip.js || npm run build:addon) sh: /build/node_modules/.bin/cross-env: /usr/bin/env: bad interpreter: No such file or directory npm ERR! code ELIFECYCLE npm ERR! errno 126
... trying to build https://github.com/nodegui/svelte-nodegui-starter
remove scrambled output from
npm install
progress is enabled by default instead of
--no-progress
, we could also usenpm config set progress=false
for debugging, we could use
--verbose
ornpm config set verbose=true
but this is too verbose for normal usethe root cause for the scrambled output is probably a buffer issue so that
\r
is parsed wrongbefore
after
... trying to build https://github.com/nodegui/svelte-nodegui-starter