Open hesxenon opened 3 months ago
You are welcome to bundle things and then not use the resulting bundle (and not write the bundle to the file system, with write: false
). But bundling is required for esbuild to process the whole module graph. If you don't bundle, then esbuild doesn't traverse through the module graph at all.
I'm having trouble figuring out how to basically copy the whole library and transpile it along the way without bundling.
The reason for why I don't want to enable bundling is to enable downstream projects to utilize tree shaking as much as possible (i.e. I don't want to deal with that).
Just using
tsc
without an outdir has been fine so far but now I need to have multiple outdirs and that obviously breaks my asset imports. Rather than watching those assets myself and copying them into each outdir on change I thought I'd just use esbuild for that only to notice thatbundle: false
only copies the entrypoints instead of everything that's referenced by that entrypoint.So given the following input
and
what I'd like to have in my outdirs is
Is there a way to enable that with esbuild?