Update TypeScript compilation target to es2022 for node rigs and projects#5667
Draft
Update TypeScript compilation target to es2022 for node rigs and projects#5667
Conversation
…ects Co-authored-by: dmichon-msft <26827560+dmichon-msft@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Update default target for node rigs to minimum supported version
Update default TypeScript compilation target to es2022 for node rigs and projects
Feb 24, 2026
…< 1.0.0 Co-authored-by: dmichon-msft <26827560+dmichon-msft@users.noreply.github.com>
Copilot
AI
changed the title
Update default TypeScript compilation target to es2022 for node rigs and projects
Update TypeScript compilation target to es2022 for node rigs and projects
Feb 24, 2026
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.
The rushstack repo's minimum supported Node.js is 18.15.0, which fully supports ES2022, but node rigs were still defaulting to es2017/es2018 and many projects had accumulated stale target overrides (some with unresolved TODO comments referencing ES2020 as the goal).
Rig defaults updated
@rushstack/heft-node-riges2017es2022local-node-riges2018es2022decoupled-local-node-riges2018es2022@rushstack/heft-vscode-extension-riges2017es2022Stale project-level overrides removed
ts-command-line,heft-jest-plugin,eslint-plugin,operation-graphall had inline comments like// TODO: Remove when the repo is updated to ES2020— those overrides are now gonewebpack5-module-minifier-plugin,webpack5-localization-plugin,webpack4-module-minifier-plugin,preserve-dynamic-require-plugin,webpack-deep-imports-plugin,webpack-workspace-resolve-plugin) and libraries (lookup-by-path,worker-pool,localization-utilities,module-minifier)es2022acrossbuild-tests/,build-tests-subspace/, andbuild-tests-samples/Not changed
heft-web-rig,local-web-rig, and browser-targeting projects — independent of Node.js versionheft-typescript-v2-test,heft-typescript-v3-test— TypeScript ≤3.x predateses2022target supportChange files
majorbump for 5 packages at version ≥ 1.0.0 (heft-node-rig,ts-command-line,webpack5-module-minifier-plugin,heft-jest-plugin,heft-vscode-extension-rig)minorbump for 11 packages at version < 1.0.0💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.