Skip to content
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

Merged
merged 4 commits into from
Feb 2, 2024
Merged

Conversation

mwskwong
Copy link
Contributor

@mwskwong mwskwong commented Dec 31, 2023

According to

es2023 is not a valid value for lib and target. I propose using esnext for now (which is equivalent to es2023 in a sense) and keep monitoring the status, since once es2023 is available, esnext is likely equivalent to es2024 by that time.

typescript/tsconfig.node18.json Outdated Show resolved Hide resolved
typescript/tsconfig.node20.json Outdated Show resolved Hide resolved
@Ethan-Arrowood
Copy link
Contributor

Screenshot 2024-01-31 at 14 22 15

@mwskwong
Copy link
Contributor Author

mwskwong commented Feb 1, 2024

@Ethan-Arrowood Updated accordingly. However, I noticed https://github.com/tsconfig/bases/blob/main/bases/node20.json suggests the target for Node 20 should also be es2022. See whether you wish to have that aligned as well.

@Ethan-Arrowood
Copy link
Contributor

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!

@mrmckeb mrmckeb changed the title fix: es2023 is not valid fix(eslint): es2023 is not valid Feb 1, 2024
@mrmckeb mrmckeb changed the title fix(eslint): es2023 is not valid fix(typescript): es2023 is not valid Feb 1, 2024
@mrmckeb mrmckeb merged commit 3d9dbdc into vercel:canary Feb 2, 2024
6 checks passed
@mrmckeb
Copy link
Contributor

mrmckeb commented Feb 2, 2024

Thanks for the PR @mwskwong, and for the review @Ethan-Arrowood!

@vercel-release-bot
Copy link
Collaborator

🎉 This PR is included in version 5.2.0-canary.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

@vercel-release-bot
Copy link
Collaborator

🎉 This PR is included in version 5.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants