This repository was archived by the owner on Apr 24, 2022. It is now read-only.
npm-check-updates#24
Open
brettz9 wants to merge 8 commits intomocha-community:masterfrom
Open
Conversation
…peerDeps. when performing auto-update
Closed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Builds on #20 .
I find the tool
npm-check-updatesvery handy for auto-updating packages to the latest versions when available (without the noise of PRs by Github services that may do the same).This PR adds an RC file for that tool which effectively ensures that when running
npm-check-updates(or the aliasncu) with the-uflag, the peer dependencies won't also be updated to only use the latest version (since one generally wishes to keep supporting older versions for a while). (See raineorshine/npm-check-updates#598 for further detail.)