You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started to analyze webpack build and got next results (on dev machine, Intel(R) Core(TM) i7-1185G7):
General output time took 1 min, 12.42 secs,
ForkTsCheckerWebpackPlugin took 57.37 secs
This looks like the best place to start some optimizations, but I was not able to find anything surfing over the internet or reading through your readme files.
While it doesn't look very bad for local development, I often need to run this for 20+ packages in ci job with limited resources. It may take an hour to bundle everything. So reducing typecheck step for each package for 10 seconds would make a difference.
I'm using node 12, webpack 4, fork-ts-checker-webpack-plugin 5.2.1. Tried 6.5.0 and it appeared to be 15 seconds slower.
So, do you have any tips on how to speed up typechecking in a CI job? I
The text was updated successfully, but these errors were encountered:
I started to analyze webpack build and got next results (on dev machine, Intel(R) Core(TM) i7-1185G7):
General output time took 1 min, 12.42 secs,
ForkTsCheckerWebpackPlugin took 57.37 secs
This looks like the best place to start some optimizations, but I was not able to find anything surfing over the internet or reading through your readme files.
While it doesn't look very bad for local development, I often need to run this for 20+ packages in ci job with limited resources. It may take an hour to bundle everything. So reducing typecheck step for each package for 10 seconds would make a difference.
I'm using node 12, webpack 4, fork-ts-checker-webpack-plugin 5.2.1. Tried 6.5.0 and it appeared to be 15 seconds slower.
So, do you have any tips on how to speed up typechecking in a CI job? I
The text was updated successfully, but these errors were encountered: