ts-loader recommends enabling the checkSyntacticErrors option when using happyPackMode in order to also catch syntax errors (see https://github.com/TypeStrong/ts-loader#happypackmode).
However it seems like this option is not available anymore. This is the error I get:
ForkTsCheckerWebpackPlugin Invalid Options
options should NOT have additional properties
ValidationError: ForkTsCheckerWebpackPlugin Invalid Options
at Object.validateOptions [as default] (./node_modules/schema-utils/src/validateOptions.js:32:11)
I could not find anything related in the changelog. Should we use eslint now to catch that kind of issues?
I wouldn't recommend using happypack anymore; fork-ts-checker-webpack-plugin by itself should be enough. (Maintainer of ts-loader here)
I tried to use happyPack because I wanted to use thread-loader, but the build time improvements are actually small compared to just using transpileOnly without thread-loader. So I am fine with not using happyPack. However I think it would be nice if we could clarify the readme of ts-loader.
What do you mean by fork-ts-checker-webpack-plugin by itself should be enough? Without any options it does not catch syntax errors e.g. const a = [{} {}].
You can use same settings as for babel-loader: https://github.com/TypeStrong/fork-ts-checker-webpack-plugin/blob/master/examples/babel-loader/webpack.config.js :)
I'm suggesting not using happypack mode essentially
https://blog.johnnyreilly.com/2018/12/you-might-not-need-thread-loader.html
I tried to use happyPack because I wanted to use thread-loader, but the build time improvements are actually small compared to just using transpileOnly without thread-loader. So I am fine with not using happyPack. However I think it would be nice if we could clarify the readme of ts-loader.
Sure - if you'd like to submit a docs PR I'll happily take a look!
thank you for all your input. i will make a PR to update the ts-loader readme.