We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Reproduction case: https://github.com/keithamus/rollup-repro/tree/expanded
Using optimizeChunks should result in the new chunk names being rendered during generation.
The previous chunk names are rendered into dependencies, and only after running generate again are the correct chunk names used.
The text was updated successfully, but these errors were encountered:
To clarify - the CLI output is giving chunk references like chunk__3 where that chunk was already merged into chunk__1 by the optimizing phase.
chunk__3
Sorry, something went wrong.
The workaround for this is to run a build like:
const rollup = require('../rollup'); rollup.rollup({ experimentalCodeSplitting: true, optimizeChunks: true, input: ['main1.js', 'main2.js', 'main3.js'] }).then(build => { return build.generate({ format: 'amd' }) .then(generated => { return build.generate({ format: 'amd' }); }); }).then(generated => { console.log(generated); }) .catch(e => { console.log(e); })
No branches or pull requests
How Do We Reproduce?
Reproduction case: https://github.com/keithamus/rollup-repro/tree/expanded
Expected Behavior
Using optimizeChunks should result in the new chunk names being rendered during generation.
Actual Behavior
The previous chunk names are rendered into dependencies, and only after running generate again are the correct chunk names used.
The text was updated successfully, but these errors were encountered: