Summary

While migrating a project from CRA to Rsbuild, I noticed an unexpected change that didn't occur six months ago. Create React App uses ForkTsCheckerWarningWebpackPlugin to adjust the severity of issues during development, changing them from error to warning. This is helpful because it prevents the error overlay from appearing in development. Previously, this behavior worked as expected until the release https://github.com/web-infra-dev/rsbuild/releases/tag/v1.5.14. After that update, warnings still show in the terminal but are no longer sent to the browser's development server.

I tried to fix it, but I'm not sure if it's the best approach. Code deduplication can be achieved. However, after https://github.com/web-infra-dev/rsbuild/releases/tag/v1.5.14, the behavior might not be as expected, since it no longer displays warnings as it did before.

I also noticed that warnings sometimes show up in the browser console, but this happens unpredictably and for reasons that aren't clear.

class TsCheckerWarningRspackPlugin {
  apply(compiler: Rspack.Compiler) {
    new TsCheckerRspackPlugin().apply(compiler);
    const hooks = TsCheckerRspackPlugin.getCompilerHooks(compiler);
    hooks.issues.tap('TsCheckerWarningRspackPlugin', issues => {
      return issues.map(issue => ({ ...issue, severity: 'warning' }));
    });
  }
}

v1.6.10 w/o fix:

v1.6.10 w/ fix:

Related Links

https://github.com/facebook/create-react-app/blob/main/packages/react-dev-utils/ForkTsCheckerWarningWebpackPlugin.js

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).