should we mock webpack internal plugin

[hardfist]

lots of community use webpack's internal plugin like definePlugin, which is not supported in rspack, so we need to fork&clone these plugins, if we mock webpack's internal plugin it may make the plugin compatible much easier

[hardfist]

cc @web-infra-dev/rspack

[underfin]

I want this, it is awesome!

[ahabhgk]

        js side                                                         rust side
new rspack.DefinePlugin(options) -> ["builtin:define", options] -> get_builtin_plugin("builtin:define")::new(options)

just like what we do for builtin loader

[underfin]

I think webpack.DefinePlugin is better,the user doesn't change anything.

[hardfist]

or we could change options in js side?

[ahabhgk]

or we could change options in js side?

bad idea

[ahabhgk]

Another benefit is we can expose more internal plugin in this way, EntryPlugin, SourceMapDevToolPlugin, etc. and for now RawOptionsApply has two responsibility: 1. js options (RawOptions) to rust options (CompilerOptions), 2. apply internal (rust) plugins, in this way RawOptionsApply can only have the first responsibility

[hardfist]

conclusion we all agree we should implement proxy plugin