-
-
Notifications
You must be signed in to change notification settings - Fork 546
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
[Feature]: Support for webpack-assets-manifest #8058
Comments
You can try to use rspack-manifest-plugin instead, it is forked from webpack-manifest-plugin and seems do the same thing with webpack-assets-manifest. The Seems there is no method to get the code generation data of asset modules. But the assets of these modules will always be emitted through |
What problem does this feature solve?
Background
Shakapacker is a popular library for handling JS bundling in Rails apps. It's the successor to
rails/webpacker
and useswebpack-assets-manifest
as a core component. There's ongoing discussion about adding Rspack as a bundler option for Shakapacker (see issue #476), but the lack of support forwebpack-assets-manifest
in Rspack is a significant roadblock.Current Progress
I've forked the original
webpack-assets-manifest
plugin and started adapting it for Rspack. Most of the test coverage is passing, but there are still some issues. You can see the current state of the refactor here: rspack-assets-manifest test results.To complete the port, Rspack needs to support or provide alternatives for the following webpack features:
codeGenerationResults
: Used in the original plugin to gather asset information.assetsInfo
: Used to store and retrieve additional information about assets.We could either:
Benefits
webpack-assets-manifest
.I'm willing to contribute to this feature's implementation, but I would need some direction on Rspack's internal architecture and best practices for adding these or equivalent features.
What does the proposed API of configuration look like?
.
The text was updated successfully, but these errors were encountered: