Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix npm output: disable live progress #105

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

milahu
Copy link
Contributor

@milahu milahu commented Sep 14, 2021

remove scrambled output from npm install

progress is enabled by default
instead of --no-progress, we could also use 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

the root cause for the scrambled output is probably a buffer issue
so that \r is parsed wrong

before

> [email protected] preinstall /build/node_modules/aws4
> /build/node_modules/.hooks/preinstall
        ......] \ postinstall:readable-stream: info lifecycle readable-str0m

> @nodegui/[email protected] 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/[email protected]~post[0m
npm ERR! errno 126

after

> [email protected] preinstall /build/node_modules/aws4
> /build/node_modules/.hooks/preinstall

> @nodegui/[email protected] 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant