When exactly do I need to "await" the params on a dynamic pages?

[Elindo586]

Summary

This code I had to change it to await:

export async function GET(request, { params }) {
  const { email: userEmail, campid: campId } = await params;

but this one works fine without the await:

export async function GET(request, { params }) {
	const { product, email: userEmail, campid: campId } = params;

Additional information

No response

Example

No response

[icyJoseph]

In Next v15, this was changed as part of something called Async APIs. Where access to some APIs is done via Promises.

This allows Next.js to track param access. Specifically, when it happens. It has to do with how asynchronous code works, but let's not get into that for now, and it helps Next.js know exactly how much work has been done up to the point where the access happens, important for pages/layouts and it is adapted into Route Handlers with a similar API.

During the whole v15 range, both sync and async access were allowed, but as of v16 only async access is allowed.

• https://nextjs.org/blog/next-15#async-request-apis-breaking-change
• https://nextjs.org/docs/app/guides/upgrading/version-16#async-request-apis-breaking-change