Repository navigation
Conversation
BREAKING CHANGE: requires node@22 or newer Node.js 20 reached end-of-life on 2026-04-30, so node@22 is now the minimum. - `engines.node` is now `>=22` and the CI matrix drops node@20 - `tsconfig.json` target moves `es2023` -> `es2024` - the `module-sync` export condition is always auto-selectable now, so the `getNodeMajorVersion() >= 22` gate and its node@20-only fixtures are gone Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Co-Authored-By: Steven <229881+styfle@users.noreply.github.com>
ijjk
approved these changes
Nov 6, 2026
Member
|
(That means we wouldn't be able to update NFT anymore in Next.js until the next Next.js major version) |
styfle
marked this pull request as draft
November 6, 2026 16:09
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.
BREAKING CHANGE: requires node@22 or newer
Node.js 20 reached end-of-life on 2026-04-30, so node@22 is now the minimum supported version.
engines.nodeis now>=22[22, 24, 26]tsconfig.jsontarget moveses2023→es2024, which node@22 supports in fullIt also clears out the version gates that can no longer be false:
"module-sync"export condition was auto-selected behind agetNodeMajorVersion() >= 22check. With node@22 as the floor that check is always true, so it is gone along withsrc/utils/node-version.tsand themodule-sync-condition-{es,cjs}-node20fixtures, which only covered the node@20 branch and were already skipped on every supported version.sharp-pnpm.jsskip and theskipOnNode20AndBelow/skipOnNode22AndAbovelists from the test harness.Generated via styfle's devbox