-
Notifications
You must be signed in to change notification settings - Fork 8.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
[typescript] continue to use the default config in development #21966
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,7 +5,10 @@ | |
"module": "esnext", | ||
}, | ||
"include": [ | ||
"src/**/public/**/*" | ||
// in the build we populate this to include **/public/**/* but | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. is the config loader okay with comments in json? i don't think this will lint There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah, typescript config can have comments, checkout |
||
// if we did that when running from source IDEs won't properly map | ||
// public files to this config file and instead just use the defaults, ie. "strict": false, | ||
// **/public/**/* | ||
], | ||
"exclude": [ | ||
"src/**/__fixtures__/**/*" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
include config.exclude?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Whoops, copy paste fumble