Skip to solution
mediumFrontend

App Router 15 — why are params and searchParams now Promises?

897 views
01

Understand the problem

Next.js 15 makes route params async to support PPR and streaming — you must await them.

app-routernextjs-15async-params
02

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.

03

Study the solution

In Next.js 15, params and searchParams are Promises — you must await them in pages, layouts, and generateMetadata to unblock Partial Prerendering and streaming.

<marker id="a" viewBox="0 0 10 10" refX="9" refY="5" markerWidt

Solution ready — 2 min read

Classified // press E to declassify

04

Join the discussion

Discussion (0)

Sign in to join the discussion.

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

Transmission complete // awaiting log

KEEP THE
STREAK ALIVE.

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

Back to track