Does not work with Webpack Multiple Target Configuration

[kube]

When using Webpack Multiple Target Configuration, e.g.

module.exports = [
  configLibrary,
  configWebApp,
  configNodeCli,
  configDenoCli,
]

Here if all of these Webpack configurations use fork-ts-checker-webpack-plugin, only the first one will be compiled.

[johnnyreilly]

Interesting. It's not been a use case of mine so I haven't considered it. Feel free to experiment and submit PRs 😀

[IIIristraM]

Looks like right now workaround is

const tsFork = new ForkTsCheckerWebpackPlugin({...});

for (const comp of compiler.compilers) {
    tsFork.apply(comp);
}

It works, but has at least one negative effect like multiple same messages on start, nevertheless in my case with fifteen configs it's more acceptable than fifteen services.

Important note is that in my case all configs build parts of one app, so I can just run checker with tsconfig that includes all corresponding folders, add apply is a way to trigger check if any parts changed.

[piotr-oles]

@kube , @IIIristraM
Please try fork-ts-checker-webpack-plugin@alpha - I've published a new version which should resolve this issue 🚀
I will close this issue to clean-up the backlog. If this release didn't solve the issue, we can re-open this :)