Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Are there any optimization tips? #684

Closed
MichaelKapustey opened this issue Dec 7, 2021 · 1 comment
Closed

Are there any optimization tips? #684

MichaelKapustey opened this issue Dec 7, 2021 · 1 comment

Comments

@MichaelKapustey
Copy link

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

@piotr-oles
Copy link
Collaborator

The plugin overhead is negligible and you should look for tips to optimize TypeScript :)
I can recommend this page: https://github.com/microsoft/TypeScript/wiki/Performance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants