Allow generating a single UMD bundle with all code

[bebraw]

I started porting a project to dnt and so far that has gone well. I bumped into a little problem, though.

It seems the UMD code the tool emits is split to follow the original module structure. In my case, that's adding extra roundtrips I would like to avoid. Instead, the target is to match the old build which emitted a single file with all the code.

I have the related PR here if you want to have a look, survivejs/sidewind#57 .

Previously I was using tsdx in my setup and I imagine it's doing exactly that or using something like a rollup to handle bundling as it's possible TS itself might not be able to handle the task.

[bebraw]

FWIW, I think tsdx is managing this case through rollup as it's bundling the built version into a single file.

My understanding is that it's not possible to achieve that with TypeScript alone as it wasn't designed with the use case in mind but please correct me if I'm wrong.

Having bundled UMD support would be a big deal for packages that target the web in particular as that avoids waterfalls of requests that would be visible in the current solution where each module receives a separate built UMD file of its own.

[Andonvr]

I believe this is relevant for me. Though my usecase might sound a bit cursed at first glance.
I'm writing a React package using Deno, and I build it using dnt. I have a documentation created using Docusaurus, in which I want to use Sandpack to showcase code snippets.

Now, during development, I can't import my built packages from npm, as they haven't been published yet. One can use sandpack with local dependencies by bundling them into a single file and passing them in, see the docs.
They suggest using tsup, so after running my package through dnt I try using tsup's JS API. However, it seems like that one doesn't run on deno yet.

So the best solution for me would be, if I could tell dnt to also spit out a single minified .js file, that I could pass into sandpack as a local dependency.

[Andonvr]

Re above:
I solved this by using esbuild, bundling & minifying the built esm module.