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
While using SMP in our webpack configuration, if I force a failure like this:
constvalue: string={}
Type '{}' is not assignable to type 'string'.ts(2322)
and then do an initial build, the type check will fail.
However, if I then save any of the code files to trigger a subsequent build (watchdog build) the build becomes successful.
Somehow the SMP plugin is swallowing the errors for the watchdog builds.
I am using ForkTsCheckerWebpackPlugin to separate my type checking which I believe some people have reported as related
to this issue here
Of course if I remove the SMP wrapper from my webpack config it all works as normal.
The text was updated successfully, but these errors were encountered:
An631
changed the title
Using SMP causes build failures to stop showing on subsequent loads (save watchdog)
Using SMP causes build failures to stop showing on subsequent builds (webpack watchdog)
Oct 21, 2021
While using SMP in our webpack configuration, if I force a failure like this:
and then do an initial build, the type check will fail.
However, if I then save any of the code files to trigger a subsequent build (watchdog build) the build becomes successful.
Somehow the SMP plugin is swallowing the errors for the watchdog builds.
I am using ForkTsCheckerWebpackPlugin to separate my type checking which I believe some people have reported as related
to this issue here
This is my plugin config and version:
Example of the problem:
Of course if I remove the SMP wrapper from my webpack config it all works as normal.
The text was updated successfully, but these errors were encountered: