Suppress npm update notifier - #21363
Open
wborn wants to merge 1 commit into
Open
Conversation
Signed-off-by: Wouter Born <github@maindrain.net>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Suppress the npm update notifier by setting
NPM_CONFIG_UPDATE_NOTIFIER=falseforfrontend-maven-pluginexecutions.Without this, npm can periodically print its update notification to stderr, which Maven reports as errors:
These messages do not indicate a build failure but make the build output unnecessarily look like it contains errors.
Testing
Remove npm's update-notifier timestamp to force it to check for updates again:
rm ~/.npm/_update-notifier-last-checkedThen run a new build.
The npm update notice should no longer be shown. The
_update-notifier-last-checkedfile should also remain absent, confirming that the update notifier was disabled rather than merely suppressed because npm had recently checked for updates.