Repository navigation
Require Node 22 or later - #303
Merged
Merged
Conversation
Node 14-20 are EOL. Raise engines to >=22 and test on 22/24/26 in CI; publish with Node 24. - Bump @types/node to 22, and set moduleResolution explicitly so the ESM build can resolve its undici-types dependency. - Bump mocha to 11, since mocha 10 fails to start on Node 26.
This file contains hidden or 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
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.
Summary
Node 14–20 are EOL, so this drops them.
engines.node:>=14→>=22. This is a breaking change for users, so the next release should be a major version.@types/nodeto 22. Also setmoduleResolution: "node"explicitly; without it, the ESM build (--module esnext) can't resolveundici-types.mochato 11, since mocha 10 fails to start on Node 26 (yargsrequire is not defined in ES module scope).This is a prerequisite for moving the tests to Vitest (#302), which requires Node 22.12+.
Testing
npm teston Node 22, 24, and 26: 166 passingnpm run test:browser(karma, ChromeHeadless): 166 SUCCESSnpm run buildandnpm run formatpass