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

Consider using target: esnext #32

Closed
fregante opened this issue Sep 19, 2024 · 0 comments · Fixed by #33
Closed

Consider using target: esnext #32

fregante opened this issue Sep 19, 2024 · 0 comments · Fixed by #33

Comments

@fregante
Copy link
Contributor

From what I understand, target: esnext will avoid most code transforms by tsc, outputting exactly what the user authored. This is in a way similar to #29

In full-typescript projects this means that by default what you write is what you get, avoiding unwanted and often unnecessary code transforms. I think a lot of people don’t understand that “tsc acts like babel-preset” so probably this shouldn’t be the default behavior.

The advantages for this package are:

  • fewer majors required here
  • updates of this package won’t necessarily change my project’s compatibility/output

I haven’t decided what lib should be set to but that can be discussed separately, it’s fine as is.

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

Successfully merging a pull request may close this issue.

1 participant