# NextJS Support two years later

**URL:** https://community.apollographql.com/t/nextjs-support-two-years-later/8723
**Category:** Server
**Created:** [March 18, 2025, 8:54pm UTC](https://community.apollographql.com/t/nextjs-support-two-years-later/8723 "2025-03-18T20:54:32Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![David\_Bates](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/david_bates/32/5902_2.png) [@David\_Bates](https://community.apollographql.com/u/David_Bates)
#### Post date: [March 18, 2025, 8:54pm UTC](https://community.apollographql.com/t/nextjs-support-two-years-later/8723/1 "2025-03-18T20:54:32Z")

</div>

It’s been nearly two years since this post:

> [@Apollo Client support for the Next.js App Router](https://community.apollographql.com/t/apollo-client-support-for-the-next-js-app-router/6250):
>
> If you’re a Next.js user and are wondering how to use Apollo Client with the app directory, we have news for you! Read on about our new experimental support for the App Router: Blog post RFC: The Next.js “App Router”, React Server Component & “SSR with Suspense” story

What’s happening with Apollo support of NextJS? Is something non-experimental coming down the pipe?

---

<div class="post-metadata">

### Author: ![lenz](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/lenz/32/4007_2.png) [@lenz](https://community.apollographql.com/u/lenz)
#### Post date: [March 19, 2025, 8:48am UTC](https://community.apollographql.com/t/nextjs-support-two-years-later/8723/2 "2025-03-19T08:48:43Z")

</div>

Yes, we’re currently in alpha of a solution with sub-packages for Next, Remix and TanStack Start that are dropping the “experimental” in the name.

> <https://github.com/apollographql/apollo-client-nextjs/blob/next/README.md>

That said, the “experimental” part in the name was always more to draw people’s attention to carefully read the README - we have users using this in production for years and it’s very stable.

But at the same time, we wanted users to be aware of the inherent problems streaming SSR in React presents to all data fetching libraries, the fact that there are very rare edge-case sitations that can cause race conditions (that usually can be handled by this kind of helper package though, I can’t recall a report where it couldn’t), and that this is a problem that can only be solved by React with new primitives - something that hasn’t happened yet so far.

So far though, it seems that React will not be shipping those primitive anytime soon, and the “experimental” label does more bad than good, so we’ll be removing it. You don’t have to wait for the “non-experimental” release, though - you can already start using the existing library. It’s quite

---

<div class="post-metadata">

### Author: ![David\_Bates](https://sea1.discourse-cdn.com/flex019/user_avatar/community.apollographql.com/david_bates/32/5902_2.png) [@David\_Bates](https://community.apollographql.com/u/David_Bates)
#### Post date: [March 27, 2025, 8:14pm UTC](https://community.apollographql.com/t/nextjs-support-two-years-later/8723/3 "2025-03-27T20:14:12Z")

</div>

Thanks - we’ve actually been using it for over a year 🙂
