Open
Conversation
AjibadeHassan
force-pushed
the
corrected-compiler/target
branch
2 times, most recently
from
5f4ed1f to
658544a
Compare
AjibadeHassan
force-pushed
the
corrected-compiler/target
branch
from
658544a to
218bf63
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
1 participant
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.
This PR adds ES2023 and ES2024 as a valid option for the target and pattern in the TypeScript configuration schema, aligning it with the latest ECMAScript standard. This ensures users can take advantage of new language features without encountering validation issues. I tested the updated schema locally and verified that ES2023 and ES2024 works as expected. Please let me know if any changes are needed — happy to adjust!