Deal with the node globals gotcha

[tmcw]

The node globals gotcha looks like this:

1. Unlike Node.js, Deno does not have process or Buffer globals in files by default.
2. The Node.js @types/node TypeScript type definitions defines global process and Buffer objects
3. Many NPM modules rely on the @types/node type definitions
4. When you import a module that relies on @types/node, then it loads those types, and then makes process and Buffer objects appear to be global, from the perspective of the typechecker. But they do not actually become globals: this is just a type system problem.

We have considered some solutions to this:

• Replace all references to @types/node with a custom patched version
• Patch @types/node when we detect that it is being loaded into the type environment
• Try to "un-set" process and Buffer in the environment

There is no robust solution that I've found to this yet.

[zephraph]

Thankfully it looks like this problem is taking care of itself. Deno 2 adopts Node globals.