Webpack compatible builtins should also be available via new rspack.XXXPlugin()

[h-a-n-a]

What problem does this feature solve?

This blocked some tests in Rspack. https://github.com/webpack/webpack/blob/6be4065ade1e252c1d8dcba4af0f43e32af1bdc1/test/configCases/loaders/hot-in-context/webpack.config.js

What does the proposed API of configuration look like?

Make every webpack compatible builtins to be registered using plugins: [new rspack.xxxPlugin()].

[h-a-n-a]

This can be introduced in a progressive way.

1. On the top of builtins, we add support for plugin style and at the same time, deprecating the builtins options
2. Fully support for plugin style

[ScriptedAlchemy]

We should throw deprecation warnings for builtins before removing it completely so users have a chance to adopt before build fails.

[9aoy]

I am more concerned about how rspack will set the minimizer behavior. Built-in minimizer is a default value in webpack, and only override is supported, and experiments.css does not yet support built-in compression (webpack/webpack#14893).

ps. In our scenario(modern.js), we want to continue using rspack's built-in js minimizer, but replace css minimizer with cssnano.

[9aoy]

It seems that the webpack experiment css is supporting minimize, but I am more concerned about whether I can use the built-in js compression and custom css compression at the same time. 😂

webpack/webpack#17309

[h-a-n-a]

closed in favor of this #4006