-
Notifications
You must be signed in to change notification settings - Fork 47.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: remove devEngines
declaration in root package
#32398
Merged
poteto
merged 2 commits into
facebook:main
from
michaelfaith:chore/fix-devEngines-declaration
Feb 16, 2025
Merged
chore: remove devEngines
declaration in root package
#32398
poteto
merged 2 commits into
facebook:main
from
michaelfaith:chore/fix-devEngines-declaration
Feb 16, 2025
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 change removes the `devEngines` declaration in the root package. It didn't match the package.json spec and in npm 10.9.0 (released in October), a breaking change was introduced that checks the `devEngines` property. This causes `npm pack` calls to fail, due to the malformed `devEngines`. Since there's already an `.nvmrc` defined in the repo, and no strong need to enforce a specific node version for local development, this removes the declaration altogether.
4a18dc7
to
035de31
Compare
devEngines
declaration in root packagedevEngines
declaration in root package
Thanks! For context @michaelfaith and I discussed this offline, and we agreed that there's little value in enforcing local node versions unless one is building from source locally (which is convoluted anyway due to requiring an old version of Java). Since we already enforce this in CI in order to ensure builds work it seems fine to remove. |
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 change removes the
devEngines
declaration in the root package. It didn't match the package.json spec and in npm 10.9.0 (released in October), a breaking change was introduced that checks thedevEngines
property. This causesnpm pack
calls to fail, due to the malformeddevEngines
. Since there's already an.nvmrc
defined in the repo, and no strong need to enforce a specific node version for local development, this removes the declaration altogether.