Next.js 13.4 Edge Runtime: Choosing a Portable API Surface for Cancellation and Timeout Handling

Goal

Build edge‑middleware that can be deployed on Vercel, Netlify, and Cloudflare without vendor‑specific code, while still responding to request cancellations and respecting platform timeout limits.

Constraints

• Edge Runtime removes Node.js built‑ins (fs, path, Buffer, etc.) and exposes only a subset of Web APIs.
• Each platform implements a different subset of the WinterCG proposal and offers distinct cancellation mechanisms (e.g., Vercel aborts the isolate, Cloudflare exposes event.waitUntil(), Netlify has no documented signal).
• Timeout budgets vary (Vercel 10–30 s, Cloudflare 10–30 s, Netlify 26 s), and graceful shutdown hooks are absent.

Unresolved Decision

Should middleware target the WinterCG minimum API to achieve write‑once‑deploy‑anywhere portability, or rely on platform‑specific extensions (KV, durable objects, image optimization) that lock deployments to a single provider but offer richer capabilities?

Specific Questions

1. What is the recommended way to propagate a request‑level AbortSignal to downstream async operations in a portable edge middleware?
2. How can we implement graceful timeout handling that respects each platform’s limits while remaining compatible with the WinterCG surface?
3. Is there a common, documented API or polyfill that can detect and react to timeout events across Vercel, Netlify, and Cloudflare?