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

Is "es2021" target/lib valid? #50

Closed
bwdotdev opened this issue May 8, 2021 · 3 comments
Closed

Is "es2021" target/lib valid? #50

bwdotdev opened this issue May 8, 2021 · 3 comments

Comments

@bwdotdev
Copy link
Contributor

bwdotdev commented May 8, 2021

I daily run Node 16 so it is natural that when creating new projects, one of the first things I do is yarn add --dev @tsconfig/node16.

This does however present an issue; the node16 tsconfig contains es2021 as it's "target" and "lib" which causes TypeScript to scream at me both within my IDE (VS Code) and upon compiling my project.

I assumed I had an old version of typescript installed or similar but upon checking the Official Documentation, I have discovered that es2021 is not actually a valid property.

Should this become ESNext instead until ES2021 is supported?

Also, as a side note, all of the configs currently specify the ECMA version in lowercase (es2020), whilst the documentation uses uppercase (ES2020); these should probably be updated to follow the documentation.

@vukbgit
Copy link

vukbgit commented May 9, 2021

same thing happening to me, same thoughts and doubts...

@orta
Copy link
Member

orta commented May 9, 2021

es2021 exists in the current 4.3 beta ( which got an rc last week) - I'm open to moving this back to es2020 though 👍🏻

@bwdotdev
Copy link
Contributor Author

bwdotdev commented May 9, 2021

@orta Created PR 👍🏻

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

No branches or pull requests

3 participants