-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
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
Minor performance improvements #7587
Conversation
- use ESLint cache - disable syntactic errors check in fork-ts-checker - remove useless `watch` option in fork-ts-checker
quick question. 2/3 of your points its about typescript users. Are those changes can affect users that dont use typescript? maybe instead of delete or change those options use the |
@eladmotola Well, those 2 options are already in |
@deftomat a note to myself - check the hole file first... thank you for the answer |
Looks like automated tests are broken as errors are not related to these changes 😞 |
Thanks for the PR @deftomat. It looks like all |
@ianschmitz Good catch. But we still don't need it as Babel will catch these issues anyway. But it is up to you, should I revert that flag? Anyway, the only noticeable performance benefit is ESLint cache. |
Thanks! I reverted the |
Enable ESLint cache:
We discovered that enabling the ESLint cache can reduce the time for full rebuild. In our project, the time for a warm start decreased from 20 seconds to 17 seconds.
Disable syntactic errors check:
According to documentation,
fork-ts-checker
can check for syntactic errors. This is basically useless for us as Babel already report those errors.Remove useless
watch
option:According to documentation,
fork-ts-checker
ignores thewatch
option whenuseTypescriptIncrementalApi: true
.