Dynamic params

params and searchParams are plain synchronous objects you read directly without awaiting.

officialNext.js docs (Pages Router and v13 to v14 era)confidence 35%current as of Jan 2024

Before Next.js 15 params and searchParams were plain objects. You read a route value like params.id directly with no await. This was correct through Next.js 14. It throws on Next.js 15 and later where these props are async.

Related claims

is superseded by

On Next.js 15 and newer params and searchParams are Promises. You must await them in a page, layout or route handler.

Next.js 15 made params and searchParams async then Next.js 16 removed synchronous access. Reading them as plain objects was correct before yet throws now.