Deno 2.0

Deno 2.0 is rolling out as the biggest update since Deno 1.0, aiming to make the runtime feel less like a separate ecosystem and more like a drop-in evolution of Node—while tightening security boundaries and smoothing developer experience. The release candidate being cut for Deno 2.0 bundles major changes to globals, dependency management, permissions, stabilized APIs, and removed/soft-deprecated Node-era compatibility layers.

The most consequential shift is how Deno handles “server-like” globals. Deno 2 removes the `window` global and instead introduces `process`, aligning better with common Node expectations. That matters because many libraries probe for `window` to decide whether they’re running in a browser; keeping `window` globally available in a server runtime can trigger subtle misbehavior and a class of bugs that wouldn’t happen in Deno without it. At the same time, `process` is widely requested and often relied on by frameworks and configuration code. Deno 2 still encourages explicit imports—adding a new lint rule to steer users away from implicit globals and toward `import process from