Targeted shimming

[dsherret]

Right now the shim is too broad, for example #36 and the shim being injected for something like setTimeout and setInterval. It is also not ideal for any package that uses the shim to have to depend on undici because of deno.ns.

1. We should probably only use deno.ns for the deno namespace shimming and everything else can be injected into the build output based on if it's used.
2. Maybe instead of having deno.ns as a dependency of the output, we could analyze which parts of the Deno namespace are used and then bundle those parts in the final output.

[bebraw]

Do you think it would make sense for the users to say target browser only? Then it might be simpler on your end (no need for analysis).

[zandaqo]

Do you think it would make sense for the users to say target browser only? Then it might be simpler on your end (no need for analysis).

or simply opt out (in) of using shims in general.

[zandaqo]

I've just tried 0.7.2, now it doesn't shim Response/Request in the resulting js files, but still uses it in declaration files. That is, type Response turns into denoShim.Response.

[dsherret]

This is implemented and released now. See https://github.com/denoland/dnt#shims for more details.