Run ForkTsCheckerWebpackPlugin with async when CI env is used #6209
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #5820
To briefly summarise:
ForkTsCheckerWebpackPlugin
is run withasync: false
due to screen clearing issues hiding console errors, the unfortunate side-effect being that the recompilations take several seconds instead of less than 300ms.When the
CI
environment variable is set the screen is not cleared so the "errors being hidden" issue cannot be present. In that caseasync
can be set totrue
to have much faster compilation times. Then users who wish to usetypescript
and would prefer to have their development experience be drastically faster and won't mind the screen not being cleared can simply setCI
in theirpackage.json
.