-
Notifications
You must be signed in to change notification settings - Fork 472
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
[Bug]: failed to retrieve chunk name #6078
Comments
Rspack does not support |
Thanks. |
@h-a-n-a |
@theninthsky Yes, we can support this and PR is welcome. |
Hi, @h-a-n-a. I'm also very interested in this fix, as I think this is the exact issue that's preventing me from migrating to Rspack. My team has a django app that relies on a manifest file to look up build chunks when rendering html files. This same bug prevents the chunks from being mapped into the manifest file. ReproWhen I use the same config with both Webpack and Rspack, the output file yields different results. webpack.config.js: import BundleTrackerPlugin from 'webpack-bundle-tracker';
export default {
plugins: [new BundleTrackerPlugin({ filename: `stats.json` })],
entry: './src/index.js',
output: {
filename: 'main.js',
},
}; Manifest from Rspack {
"status": "done",
"assets": {
"main.js": {
"name": "main.js",
"path": "/Users/user/dev/webpack-demo/dist/main.js"
},
"main.js.map": {
"name": "main.js.map",
"path": "/Users/user/dev/webpack-demo/dist/main.js.map"
}
},
"chunks": {}
} Manifest from Webpack {
"status": "done",
"assets": {
"main.js": {
"name": "main.js",
"path": "/Users/user/dev/webpack-demo/dist/main.js"
}
},
"chunks": {
"main": ["main.js"]
}
} |
System Info
Operating System: Windows 11
Node Version: 20.11.1
Rspack CLI Version: 0.5.9
Details
Reproduce link
No response
Reproduce Steps
Create the following optimization in a project (coming from Webpack):
The purpose of this splitChunks configuration is to extract dependencies from async chunks and combine them.
A thorough explanation can be found here:
https://github.com/theninthsky/client-side-rendering?tab=readme-ov-file#preventing-duplicate-async-vendors
The text was updated successfully, but these errors were encountered: