Add Deno global namespace (#1748)

Resolves #1705

This PR adds the Deno APIs as a global namespace named `Deno`. For backwards
compatibility, the ability to `import * from "deno"` is preserved. I have tried
to convert every test and internal code the references the module to use the
namespace instead, but because I didn't break compatibility I am not sure.

On the REPL, `deno` no longer exists, replaced only with `Deno` to align with
the regular runtime.

The runtime type library includes both the namespace and module. This means it
duplicates the whole type information. When we remove the functionality from the
runtime, it will be a one line change to the library generator to remove the
module definition from the type library.

I marked a `TODO` in a couple places where to remove the `"deno"` module, but
there are additional places I know I didn't mark.

1 files changed, 10 insertions, 7 deletions

diff --git a/js/errors.ts b/js/errors.ts
index cd68003f9..452b2372e 100644
--- a/js/errors.ts
+++ b/js/errors.ts
@@ -5,14 +5,17 @@ export { ErrorKind } from "gen/msg_generated";
 /** A Deno specific error.  The `kind` property is set to a specific error code
  * which can be used to in application logic.
  *
- *     import { DenoError, ErrorKind } from "deno";
- *     try {
- *       somethingThatMightThrow();
- *     } catch (e) {
- *       if (e instanceof DenoError && e.kind === ErrorKind.Overflow) {
- *         console.error("Overflow error!");
+ *       try {
+ *         somethingThatMightThrow();
+ *       } catch (e) {
+ *         if (
+ *           e instanceof Deno.DenoError &&
+ *           e.kind === Deno.ErrorKind.Overflow
+ *         ) {
+ *           console.error("Overflow error!");
+ *         }
  *       }
- *     }
+ *
  */
 export class DenoError<T extends ErrorKind> extends Error {
   constructor(readonly kind: T, msg: string) {