Skip to content
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

Add package.json engine requirement for Node <20, to help contributors use compatible Node version #52955

Closed

Conversation

domdomegg
Copy link
Contributor

Partially addresses #52943

There's a PNPM bug that stops PNPM 7.24.3 working on Node 20: pnpm/pnpm#6424. We previously tried updating PNPM to fix this (#51406), but this was reverted due to issues (#51539).

While we wait on a longer term solution (discussing in #52943), this temporary solution will help new contributors figure out what's going wrong sooner. The current experience is to get a few warnings and then get stuck: this will change the behaviour so it clearly asks people to use a different Node version.

@@ -243,7 +243,7 @@
"@types/react-dom": "18.2.4"
},
"engines": {
"node": ">=16.8.0"
"node": ">=16.8.0 <20"
},
"packageManager": "pnpm@7.24.3"

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could just bump this to the latest v7 version, and you wouldn't need to restrict the node version to <20; this issue was fixed in 7.32.2+ and 8.3.1+.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oops, you said there were issues and I ignored that, my mistake.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That being said, there have been fixes since 7.32.2 so, maybe it works?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed bumping PNPM may work - but while it's unclear whether this will break things (awaiting confirmation on what broke last time, given CI didn't catch it), I think this will be useful as an interim measure.

@domdomegg
Copy link
Contributor Author

Superceded by #50923

@domdomegg domdomegg closed this Aug 18, 2023
@github-actions github-actions bot added the locked label Sep 1, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants