fix: explicit allow engine npm@10 - #1107
Merged
Merged
Conversation
Signed-off-by: Joona Heinikoski <joona.heinikoski@reaktor.com>
Closed
jkowalleck
changed the title
npm@10
jkowalleck
changed the title
npm@10npm@10
Member
jkowalleck
added a commit
that referenced
this pull request
Sep 18, 2023
Signed-off-by: Jan Kowalleck <jan.kowalleck@gmail.com>
Member
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
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.
#974 introduced support for npm 10, but package.json engines field was left with just npm 6 - 9. This tiny PR updates the engines field to npm 6 - 10, so npm 10 can be used without
--ignore-enginesflag.This PR doesn't introduce any functional changes.