Package management improvement idea #462
Merged
Conversation
This file contains 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.
I like to use
npm-check-updatesin my personal projects and thought it could be useful here too. I added some npm scripts to help with managing packages.npm run deps:patch,npm run deps:minor, andnpm run deps:latestwill update the package.json file to the specified versions and then runningnpm iwill install those. I rannpm run deps:patchin this PR as an example.With a lot of dev deps it can be a hassle to keep everything up to date with the latest, and falling behind on that can be an even bigger burden later when trying to update anything for a legitimate reason such as new feature or security.