baseConfig export from rspack is broken, baseConfig for webpack might be broken as well

[Judahmeek]

bin/shakapacker-config --doctor seems to create a number of additional config files, but it doesn't change the result of bin/shakapacker, nor do they seem to contain anything of substance:

That's because there is no configuration there, which is an erroneous state & evidence supporting my hypothesis. However, after testing my hypothesis, I discovered that the error wasn't caused by your code, but rather our library.

I apologize for that. Fortunately, while baseConfig is apparently broken, generateRspackConfig does work, although it may provide more configuration than you'd like. Please feel free to try my fork to confirm this. I've submitted a PR with the fix.

Originally posted by @Judahmeek in #827

[Louis-T]

Hi, I don't know if I should open another issue for this (since it is about baseConfig export from rspack) but the swc loader config when using rspack is not using the config/swc.config.js.

The loader config is simply hard coded, whereas in the webpack config, the hard coded config is merged with the config from config/swc.config.js.

Rspack base loader config : rules/rspack.ts

Webpack base loader config : rules/swc.ts (imported from rules/webpack.ts)

We can get by by modifying the config afterwards, but it could be nice to be able to override the rspack's swc loader config with the swc.config.js like in the webpack usage.

Thanks