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
Copy file name to clipboardExpand all lines: README.md
+28-15Lines changed: 28 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,7 +106,7 @@ Options for the TypeScript checker (`typescript` option object).
106
106
|`configOverwrite`|`object`|`{ compilerOptions: { skipLibCheck: true, sourceMap: false, inlineSourceMap: false, declarationMap: false } }`| This configuration will overwrite configuration from the `tsconfig.json` file. Supported fields are: `extends`, `compilerOptions`, `include`, `exclude`, `files`, and `references`. |
107
107
|`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`. |
108
108
|`build`|`boolean`|`false`| The equivalent of the `--build` flag for the `tsc` command. |
109
-
|`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 files emitted by the `ts-loader`. |
109
+
|`mode`|`'readonly'` or `'write-tsbuildinfo'` or `'write-dts'` 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 files emitted by the `ts-loader`. If you use `ts-loader` with `transpileOnly` flag set to `true`, use `'write-dts` to emit the type definition files. |
110
110
|`diagnosticOptions`|`object`|`{ syntactic: false, semantic: true, declaration: false, global: false }`| Settings to select which diagnostics do we want to perform. |
111
111
|`extensions`|`object`|`{}`| See [TypeScript extensions options](#typescript-extensions-options). |
112
112
|`profile`|`boolean`|`false`| Measures and prints timings related to the TypeScript performance. |
@@ -299,24 +299,37 @@ When we call this method with a [webpack compiler instance](https://webpack.js.o
299
299
[tapable](https://github.com/webpack/tapable) hooks where you can pass in your callbacks.
Copy file name to clipboardExpand all lines: src/plugin-options.json
+2-1Lines changed: 2 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -129,9 +129,10 @@
129
129
"enum": [
130
130
"readonly",
131
131
"write-tsbuildinfo",
132
+
"write-dts",
132
133
"write-references"
133
134
],
134
-
"description": "`readonly` keeps all emitted files in memory, `write-tsbuildinfo` which writes only .tsbuildinfo files and `write-references` which writes both .tsbuildinfo and referenced projects output"
135
+
"description": "`readonly` keeps all emitted files in memory, `write-tsbuildinfo` which writes only .tsbuildinfo files, `write-dts` writes .tsbuildinfo and type definition files, and `write-references` which writes both .tsbuildinfo and referenced projects output"
0 commit comments