feat: set engines and prerelease for npm 10 #6674
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
lukekarrys
force-pushed
the
npm-10-engines
branch
4 times, most recently
from
5cfb487
to
190b7bc
Compare
BREAKING CHANGE: npm now supports node `^18.17.0 || >=20.5.0`
lukekarrys
force-pushed
the
npm-10-engines
branch
from
190b7bc
to
622c303
Compare
ljharb
added a commit
to nvm-sh/nvm
that referenced
this pull request
Jul 26, 2023
…upported nodes See npm/cli#6674
6 tasks
DaveS143
added a commit
to DaveS143/cli
that referenced
this pull request
Aug 26, 2023
This reverts commit b6cf113.
|
@lukekarrys now that v10 is out, could you update the npm registry page accordingly?
|
|
@ylecuyer that's just the readme.md in the cli. You can make a PR yourself if you want or wait for us to get to it https://github.com/npm/cli/blob/latest/README.md#requirements |
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.
BREAKING CHANGE: npm now supports node
^18.17.0 || >=20.5.0Closes npm/statusboard#640