-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(typescript): es2023
is not valid
#84
Conversation
@Ethan-Arrowood Updated accordingly. However, I noticed https://github.com/tsconfig/bases/blob/main/bases/node20.json suggests the |
Oh good point. Yeah I guess so. I think something is off with the timing (Node18 specifically) and it confused me. Thanks for contributing this! |
es2023
is not valides2023
is not valid
Thanks for the PR @mwskwong, and for the review @Ethan-Arrowood! |
🎉 This PR is included in version 5.2.0-canary.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 5.2.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
According to
es2023
is not a valid value forlib
andtarget
. I propose usingesnext
for now (which is equivalent toes2023
in a sense) and keep monitoring the status, since oncees2023
is available,esnext
is likely equivalent toes2024
by that time.