First of all, this is a great plugin, appreciate the work!
Current behavior
We are setting build: true in order to leverage project references(which is working as expected). Furthermore, we want to skip the cache and force the build when building for production. I tried to add --force option to compilerOptions, but then it complains about TS5093: Compiler option '--verbose' may only be used with '--build'. Adding the build option to compilerOptions again doesn't seem to do anything either.
Expected behavior
That I can use compiler options like --force--verbose when build: true is set.
Or some workarounds that can avoid reusing the tsconfig.tsbuildinfo cache, thanks!
Steps to reproduce the issue
Set up the plugin with config as following:
var forkTsCheckerPlugin = new ForkTsCheckerWebpackPlugin({
typescript: {
build: true,
configOverwrite: {
compilerOptions: {
force: true,
},
}
}
});
Hi! According to tsconfig.json documentation these is no such option as force. You can use it with CLI, but not with config file. Therefore, having support for force flag is a feature request - not a bug :)
First of all, this is a great plugin, appreciate the work!
Current behavior
We are setting
build: true
in order to leverage project references(which is working as expected). Furthermore, we want to skip the cache and force the build when building for production. I tried to add--force
option to compilerOptions, but then it complains aboutTS5093: Compiler option '--verbose' may only be used with '--build'.
Adding thebuild
option to compilerOptions again doesn't seem to do anything either.Expected behavior
That I can use compiler options like
--force
--verbose
whenbuild: true
is set. Or some workarounds that can avoid reusing thetsconfig.tsbuildinfo
cache, thanks!Steps to reproduce the issue
Set up the plugin with config as following:
Issue reproduction repository
Environment