Skip to content

Commit

Permalink
Make maxctrl and maxgui output less verbose
Browse files Browse the repository at this point in the history
The --no-progress option would normally be the answer but currently it
is broken due to a bug in NPM: npm/cli#3314
  • Loading branch information
markus456 committed Jul 13, 2022
1 parent 7cd5aec commit e8d8a37
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 5 deletions.
8 changes: 5 additions & 3 deletions maxctrl/build.sh
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,8 @@ then
fi
fi

npm install --production
npm install --production pkg@5
node_modules/pkg/lib-es5/bin.js --options max_old_space_size=4096 $opts -t node10-linux .
# Piping the output through `tee` works around a problem in npm where it always
# prints verbose output: https://github.com/npm/cli/issues/3314
npm install --production |& tee
npm install --production pkg@5 |& tee
node_modules/pkg/lib-es5/bin.js --options max_old_space_size=4096 $opts -t node10-linux . |& tee
6 changes: 4 additions & 2 deletions maxgui/build.sh
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,9 @@ fi

cd $PWD/maxgui

# Piping the output through `tee` works around a problem in npm where it always
# prints verbose output: https://github.com/npm/cli/issues/3314
export buildPath=$PWD
export VUE_APP_GIT_COMMIT=$(cd $src && git rev-list --max-count=1 HEAD)
npm ci --production
npm run build
npm ci --production |& tee
npm run build |& tee

0 comments on commit e8d8a37

Please # to comment.