Vercel Releases Stability

Node-only API in edge runtime

Part of the Edge runtime readiness check · fix arrives as a guide

What it is

Edge-runtime code uses a Node-only API — fs, crypto in its Node form, Buffer, process, or a Node built-in module.

Why it matters

The edge runtime implements Web APIs, not Node's. The build may pass and the failure arrive on first invocation, which means it reaches production before anyone sees it.

How to fix it

Replace with the Web equivalent — crypto.subtle, TextEncoder, fetch — or move the route to the Node.js runtime if it genuinely needs Node APIs.

Also in Edge runtime readiness

Node-incompatible or oversized dependency in edge runtime VercelEdge runtime readiness Heavy DB/network work in middleware.ts VercelEdge runtime readiness Middleware missing config.matcher (runs on all routes) VercelEdge runtime readiness Edge data-fetch route missing preferredRegion VercelEdge runtime readiness

Run them all on your app

Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.

Guard my app · Free → View pricing