Uh oh!
There was an error while loading. Please reload this page.
Remove "engines" field from package.json - #1712
Conversation
🦋 Changeset detectedLatest commit: 2da1e52 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
size-limit report 📦
|
jfuchs
left a comment
There was a problem hiding this comment.
Is engines supposed to be about what's needed to run the distributed package? Or is it about what's needed to build and contribute?
colebemis
commented
Dec 9, 2021
I think it's "what's needed to run the distributed package" because I couldn't install |
colebemis
commented
Dec 9, 2021
https://docs.npmjs.com/cli/v6/configuring-npm/package-json#engines
|
* Remove "engines" field from package.json * Create tidy-maps-care.md
The
enginesfield is breaking builds for projects using node <16. Since node 16 is not required to use@primer/react, let's remove this field from the package.json.