Open erikas-tranauskas opened 1 year ago
If you read the documentation of fork-ts-checker-webpack-plugin
, it explicitly say that you will need to run type checking separately from your webpack build when using this plugin (disabling type checking is a big part of what makes it faster)
I believe it should start this separate process by adding a plugin to webpack config.
.addPlugin(new ForkTsCheckerWebpackPlugin({ async: true }))
doesn't do much. Any idea how to start it?
Thank you for this issue. There has not been a lot of activity here for a while. Has this been resolved?
I have a long running build times and I am trying to find a way to fix it. One of the solutions could be enabling the
enableForkedTypeScriptTypesChecking
. After enabling this setting it requires to install thefork-ts-checker-webpack-plugin@^6.0.0
and it cuts the build time almost in half, but the problem is that with this option enabled, the build doesn't validate the .ts files at all. I can remove all the types from the variables in .ts files and it still compiles successfully.Any way to configure this to run smoothly?
My webpack.config.js: