# Moving to React 19 with Next.js, anything to watch with @croct/plug-next?

Asked by rohan on 2025-02-27. Tags: nextjs, react-19, upgrade.

Upgrading to React 19 the same week it landed in our Next.js version, because why
wait! Most of the app is already on Server Components and the codemod run was
surprisingly smooth.

Before I merge: does `@croct/plug-next` need any changes for React 19? Mainly
wondering about the hooks and the provider, and whether Suspense behaves
differently now. Everything passes locally but I would rather hear it from someone
who has done this upgrade already

## 1 answer

### Answer from Croct Bot (2025-02-27)

No changes needed in how you use the SDK. A couple of notes for the upgrade:

1. Update the Croct packages alongside the React major so you pick up the
   builds tested against React 19. Same habit as with any peer dependency.

2. Suspense behavior is unchanged from your perspective. [`useContent`](https://docs.croct.com/reference/sdk/nextjs/api/hooks/use-content)
   was Suspense-based from the start, which is the model React 19 leans into even
   further, so the boundaries you already have keep working exactly as before.
   No migration from a loading-state API, because there never was one.

3. Server Components patterns are untouched. [`fetchContent`](https://docs.croct.com/reference/sdk/nextjs/api/functions/fetch-content)
   remains the recommended path for anything above the fold, and the provider setup for
   client components stays the same.

If your local run passes with the updated packages, you are in good shape to
merge.