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

Using SMP causes build failures to stop showing on subsequent builds (webpack watchdog) #178

Open
An631 opened this issue Oct 21, 2021 · 0 comments

Comments

@An631
Copy link

An631 commented Oct 21, 2021

While using SMP in our webpack configuration, if I force a failure like this:

const value: 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

This is my plugin config and version:

{
      async: false,
      typescript: {
        configFile: 'tsconfig.srconly.json',
        diagnosticOptions: {
          semantic: true,
          syntactic: true,
          declaration: true,
          global: true,
        },
      },
      eslint: {
        files: "./src/**/*.{ts,tsx}",
      }
}
"fork-ts-checker-webpack-plugin": "^6.3.4",

Example of the problem:
image

Of course if I remove the SMP wrapper from my webpack config it all works as normal.

@An631 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
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

1 participant