Skip to content

Conversation

richardlau
Copy link
Contributor

npm 10.8.2 doesn't install the latest tagged version of @pkgjs/support with Node.js 22 as Node.js 22 is outside of the declared specification for engines->node.

Regardless of whether the change in behaviour of npm is correct for a semver-patch release of npm, update the engines field to include the supported Node.js release lines at this point in time.

Refs: npm/cli#7704 (comment)

@richardlau
Copy link
Contributor Author

hmm. It looks like tests are broken everywhere (even for the older Node.js versions that this PR doesn't change). 😞

@wesleytodd
Copy link
Member

We should probably just change this to >10 at this point right? Just not sure there is value in enumerating them like this?

@richardlau
Copy link
Contributor Author

richardlau commented Aug 7, 2024

We should probably just change this to >10 at this point right? Just not sure there is value in enumerating them like this?

I don't think so -- I was going with "don't disturb anything already there". I've updated the field to >=10.19 (I assume the existing ^10.19 was there for a reason).

npm 10.8.2 doesn't install the `latest` tagged version of @pkgjs/support
with Node.js 22 as Node.js 22 is outside of the declared specification
for `engines`->`node`.

Regardless of whether the change in behaviour of npm is correct for a
semver-patch release of npm, update the `engines` field to include the
supported Node.js release lines at this point in time.
@wesleytodd wesleytodd merged commit 81a010c into main Aug 8, 2024
16 checks passed
@wesleytodd wesleytodd deleted the update-engines branch August 8, 2024 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants