What problem does this feature solve?
If you build a NPM library, the code splitting can often be harmful because it reduces the readability and analyzability of the output ESM files.
This is the most wanted feature in Rollup (rollup/rollup#2756).
I want to use tsdown, a library bundler using Rolldown instead of esbuild, instead of tsup, but I cannot migrate from tsup to tsdown due to the fact rolldown and tsdown cannot disable the code splitting feature.
rolldown/tsdown#78
What does the proposed API look like?
Add config option to turn code splitting feature off.
What problem does this feature solve?
If you build a NPM library, the code splitting can often be harmful because it reduces the readability and analyzability of the output ESM files.
This is the most wanted feature in Rollup (rollup/rollup#2756).
I want to use tsdown, a library bundler using Rolldown instead of esbuild, instead of tsup, but I cannot migrate from tsup to tsdown due to the fact rolldown and tsdown cannot disable the code splitting feature.
rolldown/tsdown#78
What does the proposed API look like?
Add config option to turn code splitting feature off.
Workaround: You can now work around this issue by assigning a separate build configuration to each input.
Example: https://stackblitz.com/edit/github-ehiwc7lh-pk9i7zur?file=rolldown.config.mjs