-
Notifications
You must be signed in to change notification settings - Fork 12.3k
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
tsc --init update 2024 #58420
Comments
Module options look good to me for Node.js / library authoring. I assume you’ve intentionally left in some redundancies so that good option A stays set if someone changes/removes option B that’s currently making A redundant. For good measure, a list of those:
The one that’s missing from this good-but-redundant category is TLDR looks good 👍 |
Though originally I was thinking more about So I'm generally in favor around |
👍 / 👎 ?
|
Pretty much everybody is going to debug at some point, and it’s going to be bad until they realize they need to enable |
The only thing that sucks about having options commented out is you can't hover on them to see the description of what they do, which doesn't help when you don't know what something does and want to know if you should enable it. Unfortunately most options don't have an explicit setting that means "use the default behavior, whatever it happens to be today", so no easy solutions to be found here. |
I could also suggest turning off |
Acknowledgement
Comment
Following up from #58417
Note: This is only for argumentless
tsc --init
. We know that it's physically possible to write text after--init
and that text could do something, but that's a separate issue. Sincetsc --init
should do something, this issue is only about what that something is.General consensus from the design meeting + external discussion:
"module": "commonjs"
is a hard noOther live issues:
types
to[]
- yesudfcf
- I would argue moot by now since we should set the target high enough that this doesn't matterpackage.json
contents when creatingtsconfig.json
undertsc --init
to determine better defaults #51207 - consultpackage.json
- it's not obvious that yourpackage.json
is configured yet at the time you runtsc --init
, this seems marginalOther things we didn't get to:
rootDir
,outDir
: These are generally a good idea; no one likes the default side-by-side JS emit buuut there aren't strictly universal conventions hereProposed new output:
I tried to order this from "most likely to edit" to "least likely to edit"
The text was updated successfully, but these errors were encountered: