https://github.com/TypeStrong/fork-ts-checker-webpack-plugin
For now, we're using version 3.1.1 of this plugin. It does not report type checking result (error) to devServer. But if I upgrade to v5 with custom WebPack config, it can work as expected.
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs.
If we missed this issue please reply to keep it active.
Thanks for being a part of the Nx community! ๐
I raise the question. I spent a lot of time to debug why each of my NestJS microservices consumes 3GB of RAM during development. Each has 6 workers with 2GB memory limit. As I checked fast in newer versions of the fork-ts-checker-webpack-plugin they reduced workers number by default and improved the performance of the single worker.
[email protected] is used in following nrwl packages:
@nrwl/[email protected]
โ โโโ [email protected]
โโโฌ @nrwl/[email protected]
โ โโโฌ @nrwl/[email protected]
โ โโโ [email protected] deduped
โโโฌ @nrwl/[email protected]
โ โโโ [email protected] deduped
โโโฌ @nrwl/[email protected]
โ โโโฌ @nrwl/[email protected]
โ โ โโโ [email protected] deduped
โ โโโฌ @nrwl/[email protected]
โ โโโ [email protected] deduped
โโโฌ @nrwl/[email protected]
โโโ [email protected] deduped
Webpack 5 is not working well with [email protected] and is crashing builds. Folks from fork-ts-checker-webpack-plugin have fixed this in v6.
Since nrwl is still using the old version of fork-ts-checker-webpack-plugin, my team is unable to update our project to webpack 5.
@vsavkin @jaysoo @bcabanes @nrwl Any plans to update this dep?
Most helpful comment
I raise the question. I spent a lot of time to debug why each of my NestJS microservices consumes 3GB of RAM during development. Each has 6 workers with 2GB memory limit. As I checked fast in newer versions of the fork-ts-checker-webpack-plugin they reduced workers number by default and improved the performance of the single worker.