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
Is your feature request related to a problem? Please describe.
There are multiple values in packages/* tsconfig files which can be moved to root and only uncommon values can be overwritten.
For example,
"strict": true is present in 81/85 packages
"sourceMap": false is present in 81/85 packages
"declaration": true is present in 84/85 packages
"importHelpers": true is present in 83/85 packages
"noEmitHelpers": true is present in 83/85 packages
"inlineSourceMap": true is present in 81/85 packages
"inlineSources": true is present in 81/85 packages
Describe the solution you'd like
Move these values to root TSConfig instead.
Describe alternatives you've considered
Sticking with most common TSConfig values defined in individual packages.
Additional context
This issue was noticed while updating target to ES2018 in packages/* in #1562
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.
Is your feature request related to a problem? Please describe.
There are multiple values in packages/* tsconfig files which can be moved to root and only uncommon values can be overwritten.
For example,
"strict": true
is present in 81/85 packages"sourceMap": false
is present in 81/85 packages"declaration": true
is present in 84/85 packages"importHelpers": true
is present in 83/85 packages"noEmitHelpers": true
is present in 83/85 packages"inlineSourceMap": true
is present in 81/85 packages"inlineSources": true
is present in 81/85 packagesDescribe the solution you'd like
Move these values to root TSConfig instead.
Describe alternatives you've considered
Sticking with most common TSConfig values defined in individual packages.
Additional context
This issue was noticed while updating target to ES2018 in packages/* in #1562
The text was updated successfully, but these errors were encountered: