chore: drop Node 20 and target ES2023 - #283
Merged
Merged
Conversation
ulissesferreira
force-pushed
the
chore/drop-node20-es2023
branch
from
September 7, 2026 13:08
0c985c8 to
02ad652
Compare
- Node 18 and 20 are EOL: `engines.node` is now `^22.14.0 || ^24` in the root and all packages, enforced by the Yarn constraints, and the CI test matrix runs on 22.x and 24.x only. - Shared TypeScript `target` and `lib` settings are bumped from ES2020 to ES2023, matching the Snap packages, which already target ES2023. ES2023 adds no syntax over ES2022, and all ES2023 library features are supported on Node 22 and 24.
ulissesferreira
force-pushed
the
chore/drop-node20-es2023
branch
from
September 7, 2026 13:44
02ad652 to
fa2eba0
Compare
|
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
2 participants
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.
Explanation
Re-application of the non-ESM parts of #273, which was closed pending more confidence that the ESM migration wouldn't impact the extraction of TSX/JSX Snap UI components. This PR therefore contains no ESM-only,
ts-bridge, orlodash-eschanges — only the runtime and TypeScript toolchain bumps:Drop Node 20
engines.nodeis now^22.14.0 || ^24in the root and all packages, enforced by the Yarn constraints, and the CI test matrix now runs on 22.x and 24.x only.ES2023
targetandlibsettings are bumped fromES2020toES2023, so the library and script configs now match the Snap packages, which already declareES2023.target: ES2023emits identical code toES2022— ES2023 introduced no new syntax.lib: ES2023is type-checking only (nothing is polyfilled): it surfacesArray.prototype.findLast/findLastIndex(Node 18+), change-array-by-copytoSorted/toReversed/toSpliced/with(Node 20+), all fully supported on Node 22 and 24, i.e. exactly the versions we run after dropping Node 20.Snap manifest shasums changed because
mm-snapre-bundles with the ES2023 target.Checklist