Clear and concise description of the problem
When defining multiple build configurations (e.g., ESM, CJS, and DTS), Rollup/Rolldown runs each build sequentially, even when they are independent. This can slows down total build time in CI/CD pipelines.
Suggested solution
Add a parallel: true option or automatically detect when builds can be executed concurrently.
Each configuration shares most options (entry, plugins, external) and only differs in format/output.
So adding multiple outputs for one entry would be also nice
Alternative
Run multiple tsdown instances in parallel using npm scripts or programmatic Promise.all, but this adds complexity and is not integrated with Rollup’s lifecycle or plugin system. Will also not works with tsdown CLI
Additional context
No response
Validations
Clear and concise description of the problem
When defining multiple build configurations (e.g., ESM, CJS, and DTS), Rollup/Rolldown runs each build sequentially, even when they are independent. This can slows down total build time in CI/CD pipelines.
Suggested solution
Add a
parallel: trueoption or automatically detect when builds can be executed concurrently.Each configuration shares most options (entry, plugins, external) and only differs in format/output.
So adding multiple outputs for one entry would be also nice
Alternative
Run multiple tsdown instances in parallel using npm scripts or programmatic Promise.all, but this adds complexity and is not integrated with Rollup’s lifecycle or plugin system. Will also not works with
tsdownCLIAdditional context
No response
Validations