So if the same data would be displayed or used in both environments, it would quickly run out of sync and result in inconsistencies.

This is not the case for Server Components and they must be manually refreshed when data changes. Thanks to Apollo Client’s normalized cache, Client Components can automatically update all usages of an entity in your application, for example as a result of a mutation. When should you use Client Components vs Server Components? This library will do all the right things for you whether you’re running under Server Components or if you’re running in Client Components. In order to make it easier to adopt Apollo Client in Next.js we are releasing an experimental library: (don’t worry the name will change once the library is stable 😊). You might have seen my blog post about how to use Apollo Client with Next.js 13, and the solution we proposed worked, but it was a bit cumbersome and might break in future. While this is an exciting new feature, it also brought some confusion to people using them for the first time. The app directory is a major milestone of Next.js and the whole React ecosystem as it marks all components under the app directory as React Server Components. The latest release of Next.js 13 (13.4) declared the new app directory as stable and it will now be the default for new projects.

Express graphql