Upgrade npm to 6.x #164
Merged
Upgrade npm to 6.x #164
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
|
This pull request is automatically deployed with Now. |
|
Now v2 doesn't work at this time since the built image is over 100MB 😢 I'll have to revisit that in the future. For the time being, this will be good to bump npm version 👍 |
styfle
added a commit
that referenced
this pull request
Dec 1, 2023
Back when Package Phobia first came out in 2018, it used `npm@5` to install dependencies and measure the size. That was later upgrade to [npm@6](#164) with little behavior changed. Then upgrading node caused problems with the old version of npm so Package Phobia switched to [yarn@2](#959) and later [yarn@3](#976) which both omit peer dependencies by default. Recently, Package Phobia switched to [npm@10](#1021) which will automatically install peer dependencies. This PR will change the behavior back to omit peer dependencies. - Fixes #1025
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.
This might not be backwards compatible so I need to do some testing.
I am also upgrading the database to be able to handle more data.
Hopefully now v2 will help with the load.