Open Clarkkkk opened 1 year ago
Every time I run npm start, type checking for the first time costs over 40s. It seems incremental mode is not working. Is it a bug?
npm start
fork-ts-checker-webpack-plugin settings in webpack.config.js
webpack.config.js
new ForkTsCheckerWebpackPlugin({ async: true, typescript: { memoryLimit: 4096, build: true, mode: 'write-references', profile: true } }),
tsconfig.json
{ "compilerOptions": { "incremental": true, "target": "esnext", "module": "commonjs", "allowJs": true, "jsx": "react-jsx", "outDir": "build/dist", "removeComments": true, "importHelpers": true, "strict": true, "strictNullChecks": true, "noImplicitThis": true, "alwaysStrict": true, "noUnusedLocals": true, "noUnusedParameters": true, "noImplicitReturns": true, "noFallthroughCasesInSwitch": true, "moduleResolution": "node", "baseUrl": "./", "allowSyntheticDefaultImports": true, "esModuleInterop": true, "inlineSourceMap": true, "experimentalDecorators": true, "emitDecoratorMetadata": true, "forceConsistentCasingInFileNames": true, "skipDefaultLibCheck": true, "skipLibCheck": true, "allowUnreachableCode": true }, "include": [ "src" ], "exclude": [ "node_modules", "**/*.test.ts", "**/*.test.tsx", "build", "public" ] }
tsc --noEmit --watch --diagnostics --preserveWatchOutput
--incremental false
Time for type checking should be roughly the same as tsc.
The repository is private, but if you need a reproduction, I may find another repository to do it.
Current behavior
Every time I run
npm start
, type checking for the first time costs over 40s. It seems incremental mode is not working. Is it a bug?fork-ts-checker-webpack-plugin settings in
webpack.config.js
tsconfig.json
tsc --noEmit --watch --diagnostics --preserveWatchOutput
)--incremental false
)Expected behavior
Time for type checking should be roughly the same as tsc.
Steps to reproduce the issue
The repository is private, but if you need a reproduction, I may find another repository to do it.
Environment