Remove 'deno bundle' about now-deno HOT 2 OPEN

I think that we can continue with deno bundle for now since it is preferrable to have the smaller size and avoid adding this complexity with selecting the right files.
Maybe we should wait until a valid use case arrives and think of it with more context.

from now-deno.

I have been looking into this, and in my testing it seems that - as expected - lambdas with bundles are definitely a lot smaller than when using non bundled applications. Non bundled applications have to add source code and compiled code into the lambda, effectively doubling code size. The .deno_dir also adds .map and .meta files which also add to the total lambda size. In addition to this, all project code has to be added to the bundle because it is hard to determine what files will be used by the program as there is no clean programmatic way of getting the dep tree of a file in deno right now. deno bundle sort of has 'file level tree shaking' which defo helps to reduce lambda size.

Right now the only reason I see where non bundled code with a .deno_dir is better, would be in the case of:

• dynamic imports (those are pretty rare in backend code)
• wasm (or is this bundled?)
• plugins

What do you think?

from now-deno.