build: declare the ES2022 standard library in the tsconfigs#3706
Merged
armando-navarro merged 1 commit intoJul 9, 2026
Merged
Conversation
tyler-reitz
approved these changes
Jul 8, 2026
The lib declarations (es2018/es2019) understate every runtime this project supports — Node 20+ and the browsers Angular 21 supports all provide ES2022, and the Angular CLI generates new workspaces at ES2022. This also resolves the inconsistency of target es2020 sitting alongside lib es2018. Type-checking declaration only; compilation targets are unchanged, so emitted code is identical.
armando-navarro
force-pushed
the
chore/declare-es2022-lib
branch
from
74ea83b to
3fd961c
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.
The tsconfig
libdeclarations (es2018in the root and base configs,es2019intsconfig.build.json) understate every runtime this project supports — Node 20+ in CI and the browsers Angular 21 supports all provide ES2022, and the Angular CLI generates new workspaces at ES2022. This also resolves the inconsistency oftarget: es2020sitting alongsidelib: es2018.Type-checking declaration only; compilation targets are unchanged, so emitted code is identical.
Fixes #3705