It would be very useful to have direct access to the esbuild launch args. Similar to esbuildPlugins, a "esbuildParams" would be useful in one off situations where the tsup API does not provide functionality.
As an example, it would be great if we could provide an output file name and not just an outDir. The work around I've come up with for now is to write a custom plugin to rename the assets at the end.
I can absolutely appreciate the philosophy of "this is a wrapper" and for advanced cases use esbuild directly. However, I am trying to standardize our tooling and having direct access would allow us to standardize on tsup.
Upvote & Fund
We're using Polar.sh so you can upvote and help fund this issue.
We receive the funding once the issue is completed & confirmed by you.
Thank you in advance for helping prioritize & fund our backlog.
It would be very useful to have direct access to the esbuild launch args. Similar to esbuildPlugins, a "esbuildParams" would be useful in one off situations where the tsup API does not provide functionality.
As an example, it would be great if we could provide an output file name and not just an outDir. The work around I've come up with for now is to write a custom plugin to rename the assets at the end.
I can absolutely appreciate the philosophy of "this is a wrapper" and for advanced cases use esbuild directly. However, I am trying to standardize our tooling and having direct access would allow us to standardize on tsup.
Upvote & Fund