Prevent no-default-lib removing Deno global?

[dsherret]

It is quite annoying to import something and it has a /// <reference no-default-lib="true" /> directive as it will remove the Deno global. Perhaps we should look into if there's a way we could make the deno global always included even when this is specified.

[bartlomieju]

This is such a common pitfall/footgun so I'm +1 on us doing that.

[isAdrisal]

+1 to this. I came across this building a small project with Fresh for the first time (having used Deno for a bunch of things at this point), and it was very unintuitive why adding --unstable had no effect.