🔧 Update Node >=22 and npm >=11 #127
Merged
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.
Summary
Bump the required runtime engines to modern versions:
>=22>=11What Changed
package.jsonenginesfield from the previous lower requirements to{"node": ">=22", "npm": ">=11"}.Rationale
Node 22 provides:
Raising npm to 11 ensures compatibility with lockfile format / workspace and provenance improvements.
Verification
npm test).npm run pretest)../cli.js --help) works under Node 22.Impact / Risk
Migration Guidance
If a consumer is on Node 20, upgrade via nvm:
Or with volta:
Possible Follow-Ups (Optional)
readme.mdusage section.Release Note
Chore: require Node >=22 and npm >=11.
Checklist
Let me know if you’d like CI updates bundled here or in a follow-up PR.