apollo-client VS react-apollo

Actually, it's worse than that. Next has started throwing errors if it statically detects you even _importing_ hooks inside of a React Server Component environment:

- https://github.com/apollographql/apollo-client/issues/10974

- https://github.com/apollographql/apollo-client/issues/11167

To the point that Lenz Weber( a maintainer of Apollo Client, and my co-maintainer on Redux Toolkit), is considering resorting to a package that wraps and re-exports all of React's public API just to avoid that static analysis:

- https://github.com/apollographql/apollo-client/pull/11175

Apollo Client (18k ⭐) -> A comprehensive state management library for JavaScript that enables you to manage both local and remote data with GraphQL. Use it to fetch, cache, and modify application data, all while automatically updating your UI.

This currently doesn't work as expected so I have logged this issue in apollo client repo.

I understand this has something to do with the fact, that SvelteKit expects the client and server code to be completely identical - this has already prompted changes to rxjs and apollo is still pending to be fixed. I understand the reason behind being able to run rxjs and apollo on the server but

There is a long-standing issue with error caching (its absence, that is), which leads to errors being rendered as a loading state on the server side. Therefore, if you're doing SSR, you might want to design your schema in such a way that there are no intentional errors in queries whatsoever. To do so, we can use null values instead of NOT_FOUND errors (see how we essentially treated errors as data here?). Note how nothing stops us from setting the response code to 404 in case of a null value, should we want so.

Lol apollo client too.. saw this issue opened like, immediately after the release https://github.com/apollographql/apollo-client/issues/10231

There were some caching issues, outlined here https://github.com/apollographql/apollo-client/issues/6916 to be aware of

If you look at how major backend projects structure their code, it's almost always object-oriented TypeScript.

I submit for the record:

- Apollo Client: https://github.com/apollographql/apollo-client/blob/main/src...

- Storybook: https://github.com/storybookjs/storybook/blob/next/lib/chann...

- Nest: https://github.com/nestjs/nest/blob/master/packages/core/nes...

- MongoDB Driver: https://github.com/mongodb/node-mongodb-native/blob/main/src...

- Prisma: https://github.com/prisma/prisma/blob/main/packages/engine-c...

[※Alert: The following is a code example using the Apollo Client notation, but the Apollo Client does not support Suspense at this time. Github issue about Suspense support: https://github.com/apollographql/apollo-client/issues/9627]

This apollo issue matches my problem: https://github.com/apollographql/react-apollo/issues/2866

We’re heavy users of Apollo GraphQL in my team at Swarmia, but sometimes mocking the queries is bothersome. And based on a few GitHub comments, it looks like we’re not alone. This blog post is here to help!

I'm using the awesome https://github.com/apollographql/react-apollo library and I'm trying to see if there is a better convention to load data into components than how I'm doing it now.

Hello guys, I'm working with GraphQL using Apollo Client and facing a big issue but haven't found a fix yet. The problem is with fetchMore callback. This trigger twice, one is the original call, second is the call with new variables. But onComplete only return the response of the original one. When I use nextFetchPolicy: "cache-first" it not trigger the original variables anymore, but the onComplete doesn't return the result of new call. I've looking for a solution on the internet and found this: https://github.com/apollographql/react-apollo/issues/2177 But a few years passed and there aren't any explain or fix. It makes me nervous about choosing apollo client for long-term usage. Can you suggest a client that still has maintainers?

React Apollo fits perfectly the requirements, and it now supports Hooks for your GraphQL operations.

I've been using Apollo for a couple of years now, and it is infamously nebulous when it comes to moderately complex real-world scenarios, such as parameterized queries. There are many years-spanning github issues on this problem alone, with barely any maintainable solutions proffered. I've written a lengthy guide that explains exactly how Apollo's InMemoryCache works under the hood and how to sanely solve these caching issues.