chore: update typescript compiler target to ES2023 #1991
Merged
Conversation
This file contains 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
romainbrancourt
changed the title
romainbrancourt
force-pushed
the
update-ts-compiler-target
branch
from
2a5b4c9 to
83f92d0
Compare
micalevisk
approved these changes
Feb 15, 2025
There was a problem hiding this comment.
could you please update https://github.com/nestjs/typescript-starter/ as well?
|
LGTM |
12 tasks
|
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Since NestJS 11 now requires Node.js v20 or higher, Typescript compiler target can be set to ES2023 safely.
(https://github.com/microsoft/TypeScript/wiki/Node-Target-Mapping)
This enables usage of new features such as:
etc...
Does this PR introduce a breaking change?