The Edge Runtime is a sandbox with web APIs only: fetch, Request/Response, streams, crypto.subtle, TextEncoder, plus an AsyncLocalStorage polyfill. It was designed to start fast close to users. You opted a page, layout or route handler into it with export const runtime = 'edge'.
The deprecation. It landed in v16.3.0 (PR #93369; v16.2.0 doesn't contain it). The PR's whole rationale is that Edge "is being deprecated in favor of the Node.js runtime (the default)", and the message page says to delete the export, since "no replacement is needed". Neither names a removal version. What the docs show is that new work targets Node.js: Proxy runs only on Node.js since 16, and Cache Components rejects any runtime export.
What it traded away, measured on Next.js 16.4.5 (next build && next start):
- Node.js APIs.
import { readFileSync } from 'node:fs'orcreateHashfromnode:cryptofailed the build:Native module not found: node:fs.process.versionwasundefined, andnew Function()threwEvalError: Code generation from strings disallowed for this context. - Static generation and ISR. The build warned
Using edge runtime on a page currently disables static generation for that page. A page withrevalidate = 60was listed asƒand rendered anew on every request, with noCache-Controlheader at all. - Packages that need Node built-ins or
requireat runtime.
What still works: edge routes build with a warning and run. next start runs them inside a vm sandbox in its own Node process, so NEXT_RUNTIME was edge.