chore: upgrades default ts lib from es2018 + extras to full es2021 #29832
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.
Additional details
@packages/server
is compiled withesnext
libs, while other packages (even ones that depend on@packages/server
) are compiled withes2018
(+ a fewes2021
feature specific libs). This can cause ats-check
mismatch, as e.g.,@packages/net-stubbing
depends on@packages/server
. If the portions of@packages/server
that@packages/net-stubbing
imports includees2021
features, likeAggregateError
, ts-check will fail without this.This is a fairly safe change, as it does not change the target ES version - just which polyfills Typescript will include behind the scenes.
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?