Should we set '"types": []' for 'tsc init'?
See original GitHub issueVery few people understand the automatic @types
inclusion behavior, it often causes packages to conflict, and it is often a program construction performance foot-gun.
Maybe we should output a field like this in compilerOptions
.
// Add packages with global definitions that can't be imported here.
// Remove entirely to auto-include all '@types' packages.
"types": []
What do others here think?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Documentation - tsc CLI Options - TypeScript
Flag Type Default
‑‑allowJs boolean false
‑‑allowUmdGlobalAccess boolean false
‑‑allowUnreachableCode boolean
Read more >Typescript Project Configuration - Medium
I 've been working on a couple projects that are written with typescript so I've been learning here and there, but I wanted...
Read more >Generating Default TypeScript Configuration Files with tsc --init
TypeScript 1.6 introduced the --init flag for the tsc executable to make it easier to set up new TypeScript projects. A short summary....
Read more >How To Set Up a New TypeScript Project - DigitalOcean
When you write code in TypeScript, running tsc will transform or compile your code into JavaScript. Using the --init flag in the above...
Read more >How to set up TypeScript with Node.js and Express
When you initialize a package.json file, the --yes flag uses the default ... Type declarations are usually contained in files with a .d.ts ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes
Hmm, also yes