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
In projects where there are lots of errors that are kept to be fixed 'later', the number count is a great indicator for whether maintenance of the errors goes in the right direction - whether the count increases or decreases
We should make the error count as easy to access
However, when using webpack in watch/async mode, the error count is not accessible (comparing to sync mode, where errors are reported to webpack and are shown in total summary)
Feature description
This is what I get when building the project single time, without 'watch mode' on:
I'd like to get a similar summary every time the project is checked against this plugin in async mode; now it looks like this (at least in "fork-ts-checker-webpack-plugin": "^6.1.0"):
The text was updated successfully, but these errors were encountered:
Feature motivation
In projects where there are lots of errors that are kept to be fixed 'later', the number count is a great indicator for whether maintenance of the errors goes in the right direction - whether the count increases or decreases
We should make the error count as easy to access
However, when using
webpack
in watch/async mode, the error count is not accessible (comparing to sync mode, where errors are reported towebpack
and are shown in total summary)Feature description
This is what I get when building the project single time, without 'watch mode' on:

I'd like to get a similar summary every time the project is checked against this plugin in async mode; now it looks like this (at least in

"fork-ts-checker-webpack-plugin": "^6.1.0"
):The text was updated successfully, but these errors were encountered: