mediumFrontend

Middleware in Next 15 — what breaks from the 14 upgrade?

Q: Middleware in Next 15 — what breaks from the 14 upgrade?

Next 15 middleware keeps Edge by default but now supports `runtime: 'nodejs'`, async `NextRequest` helpers, and `instrumentation` sharing — update matchers and await `request` APIs. Request → middleware (edge|node) → rewrite/redirect → RSC render Edge (default) global low latency no Node fs auth + geo <rect x="

1.0k views

Understand the problem

Middleware now runs on the Node runtime option, request is async, and matching semantics tightened.

middlewarenextjs-15edge

Attempt it yourself

Sketch your approach before reading the solution — that's what interviews test.

Nudge consolestandby

Stuck? Beam a request up — the console returns a conceptual nudge that guides your logic without spoiling the implementation.

Study the solution

Next 15 middleware keeps Edge by default but now supports runtime: 'nodejs', async NextRequest helpers, and instrumentation sharing — update matchers and await request APIs.

Solution ready — 2 min read

Classified // press E to declassify

Join the discussion

Discussion (0)

No responses yet. Be the first to share what you think.

Transmission complete // awaiting log

KEEP THE
STREAK ALIVE.

Dossier 20 of 95 decoded in the Next.js track. One more won't hurt.

Back to track

Next up→

What is the difference between static and dynamic rendering in the Next.js App Router?

Continue