mirror of
https://github.com/elastic/kibana.git
synced 2025-04-20 07:48:52 -04:00
ad3e193a8a
* [typescript] continue to use the default config in development In #21865 we tried to make a separate config file that would be used for browser TS files by excluding them from the default config file and adding a second that included them. This works fine in the build, but IDE integrations rely on being able to automatically discover a `tsconfig.json` file in a parent directory of the file being edited, which doesn't work when the tsconfig.json file is found, but excludes the file being edited. In this situation IDE integrations silently fallback to the default TSConfig settings, which don't show the types of compiler errors that will become issues in CI, like implicit any warnings. This implements the original strategy we tried in #21865 of mutating the tsconfig.json file before we run the tsc in the build so that the config files select the right files at build time. * [tslint] remove browser config from default projects list since it is empty * [build/ts] fix typo
16 lines
435 B
JSON
16 lines
435 B
JSON
{
|
|
"extends": "./tsconfig.json",
|
|
"compilerOptions": {
|
|
"target": "es5",
|
|
"module": "esnext",
|
|
},
|
|
"include": [
|
|
// in the build we populate this to include **/public/**/* but
|
|
// 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__/**/*"
|
|
]
|
|
}
|