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
feat: rename tsconfig option to configFile for consistency (#436)
As ts-loader and tsconfig-paths-webpack-plugin uses `configFile` option,
the plugin should use the same for consistency.
BREAKING CHANGE: 🧨 `typescript.tsconfig` option renamed to the `tsconfig.configFile`
|`enabled`|`boolean`|`true`| If `true`, it enables TypeScript checker. |
159
159
|`memoryLimit`|`number`|`2048`| Memory limit for the checker process in MB. If the process exits with the allocation failed error, try to increase this number. |
160
-
|`tsconfig`|`string`|`'tsconfig.json'`| Path to the `tsconfig.json` file (path relative to the `compiler.options.context` or absolute path) |
161
-
|`context`|`string`|`dirname(configuration.tsconfig)`| The base path for finding files specified in the `tsconfig.json`. Same as the `context` option from the [ts-loader](https://github.com/TypeStrong/ts-loader#context). Useful if you want to keep your `tsconfig.json` in an external package. Keep in mind that **not** having a `tsconfig.json` in your project root can cause different behaviour between `fork-ts-checker-webpack-plugin` and `tsc`. When using editors like `VS Code` it is advised to add a `tsconfig.json` file to the root of the project and extend the config file referenced in option `tsconfig`. |
162
-
|`build`|`boolean`|`false`| The equivalent of the `--build` flag for the `tsc` command. To enable `incremental` mode, set it in the `tsconfig.json` file. |
160
+
|`configFile`|`string`|`'tsconfig.json'`| Path to the `tsconfig.json` file (path relative to the `compiler.options.context` or absolute path) |
161
+
|`context`|`string`|`dirname(configuration.configFile)`| The base path for finding files specified in the `tsconfig.json`. Same as the `context` option from the [ts-loader](https://github.com/TypeStrong/ts-loader#context). Useful if you want to keep your `tsconfig.json` in an external package. Keep in mind that **not** having a `tsconfig.json` in your project root can cause different behaviour between `fork-ts-checker-webpack-plugin` and `tsc`. When using editors like `VS Code` it is advised to add a `tsconfig.json` file to the root of the project and extend the config file referenced in option `configFile`. |
162
+
|`build`|`boolean`|`false`| The equivalent of the `--build` flag for the `tsc` command. |
163
163
|`mode`|`'readonly'` or `'write-tsbuildinfo'` or `'write-references'`|`'write-tsbuildinfo'`| If you use the `babel-loader`, it's recommended to use `write-references` mode to improve initial compilation time. If you use `ts-loader`, it's recommended to use `write-tsbuildinfo` mode to not overwrite filed emitted by the `ts-loader`. |
164
164
|`compilerOptions`|`object`|`{ skipLibCheck: true, sourceMap: false, inlineSourceMap: false, incremental: true }`| These options will overwrite compiler options from the `tsconfig.json` file. |
165
165
|`diagnosticsOptions`|`object`|`{ syntactic: false, semantic: true, declaration: false, global: false }`| Settings to select which diagnostics do we want to perform. |
0 commit comments