-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Support for Rspack #476
Comments
TLDR; if there's interest, let's try to get some initial proof of concept of this and then figure out best way of handling integration. FWIW I would love to see a proof of concept, but reviewing the docs of rspack, I feel there are fair few things that make it not quite out of the box experience. Different plugins, packages (something that we rely on - webpack manifest plugin is not compatible for example and needs rspack equivalent) make the migration harder and supporting both more burdensome. We've been getting some Webpack-specific support queries lately and having another setup variation will make it harder to respond to those IMO. I'd personally rather see a separate package that builts on top of/can be replacement to Shakapacker JS one, than bloating up the current one. After all, JS package is kinda optional, as long there's a manifest, the Ruby part can hook into it. Long term, maybe there's a world where there's a "base" Shakapacker JS package with webpacker/rspack/whatever adapter? |
Just leaving a note to say that we'd definitely have interest in a path toward migrating to Especially if it is built to be largely compatible. |
See #225.
Let's see if we can get a PR showing https://www.rspack.dev/guide/start/introduction works.
The text was updated successfully, but these errors were encountered: