You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tsconfig.json file was introduced around version 1.5 (or so) to store TypeScript compilation settings.
Proposal: leave configuration values being pulled from that file as the default but if it doesn't exist instead of just passing directly to no command options, attempt to pull the settings from package.json under a key of typescript
This is similar to the ideas posed in issue #4090 but instead of creating another config file it would just utilize a configuration file that already exists in a large number of projects.
The text was updated successfully, but these errors were encountered:
while I do agree that package.json is a nice place to keep all your configuration, I do not see the value of adding yet another variation (we have 2 already, tsconfig, and command line arguments). so I would punt on this one for now. assuming we have enough user demand we can revisit.
The tsconfig.json file was introduced around version 1.5 (or so) to store TypeScript compilation settings.
Proposal: leave configuration values being pulled from that file as the default but if it doesn't exist instead of just passing directly to no command options, attempt to pull the settings from package.json under a key of
typescript
This is similar to the ideas posed in issue #4090 but instead of creating another config file it would just utilize a configuration file that already exists in a large number of projects.
The text was updated successfully, but these errors were encountered: