TanStack Query
apollo-client
TanStack Query | apollo-client | |
---|---|---|
56 | 30 | |
39,711 | 19,198 | |
0.9% | 0.1% | |
9.8 | 9.8 | |
6 days ago | 8 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
TanStack Query
- Best Next.js Libraries and Tools in 2024
-
This is your sign(al) to try TanStack Query & Angular
To ensure that we get the best TanStack Query experience possible we are also encouraged to share feedback and participate in the discussion on GitHub, which you can check out here!
-
React Query Mutations Offline React-Native
I trust you found this information beneficial. For further details, please refer to the conversation on this GitHub issue here
-
Nx - Highlights of 2023
Tanstack - Tanstack has evolved to an entire ecosystem consisting of the famous Tanstack (or React) Query, Tanstack Table, now also Tanstack Router and Tanstack Form. It started with Tanstack Query, which adopted Nx and Nx Cloud. Zack talked about this collab with Dominik, and we also had Dominik on our Nx live stream. Now, all the above-mentioned Tanstack libs have adopted Nx, and there's more coming.
-
SQLSync – Stop Building Databases
"I’m building SQLSync because I want to make client-side applications easier to build without us having to reinvent the wheel each time."
Kinda ironic no?
Anyway, since the article is also about React, I can't recommend enough React Query [1] if you don't want to worry about caching data to reduce calls to the database and managing/refreshing stale data. It simplified so much my job.
[1] https://tanstack.com/query
-
React Basics: Essential Knowledge for Every React Developer
Combine state with data fetching with react-query This should be the second choice since you have to fetch data anyway Skip this option if you are using trpc or prefer not to use react-query
-
Tanstack's React Query Kicked `onSuccess`, `onError`, and `onSettled` Out of `useQuery`: Now What?!
onSuccess, onError and onSettled have been removed from Queries. They haven't been touched for Mutations. Please see this RFC for motivations behind this change and what to do instead.
-
TanStack Query(a.k.a. React Query) v5 announced
so cacheTime was really confusing because it seemed like "this is the amount time we cache data for", but that's not what it is. So a rename had to happen. We had some discussion on the public roadmap (https://github.com/TanStack/query/discussions/4252) about what it's gonna be. I'm usually against abbreviations, simply because there's always someone who doesn't understand what it means. But all other suggestions like inactiveCacheTime also had room for interpretation. gc is an abbreviation that is known well enough (think git gc), and it's also not an option that you will customize on a daily basis (usually once, globally).
-
Explicit Design, Part 6. Cross-Cutting Concerns and Extendable Infrastructure
By the way, I think that useSWR and React Query take on too much. They go too deep into the multiple application layers, making themselves no longer “non-opinionated,” and in some cases, using them becomes inconvenient. There are libraries that implement the SWR standard and do not use hooks, but there are not many of them.
-
13 Must Know Libraries for a React Developer
TanStack Query is an open source data fetching library in React developed by Tanner Linsley. It has more than 1.7 million weekly downloads on NPM and more than 35k stars on GitHub as of August 2023.
apollo-client
-
Things I wish I knew before moving 50K lines of code to React Server Components
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
-
Top React Data Fetching Libraries
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.
-
Using apollo client cache for local state
This currently doesn't work as expected so I have logged this issue in apollo client repo.
- React Server Components
-
Sveltekit SPA Mode: Prevent serverside code
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
-
Handling Apollo Errors in React
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.
-
Next.js 13: Layouts, React Server Components (async/await), Streaming
Lol apollo client too.. saw this issue opened like, immediately after the release https://github.com/apollographql/apollo-client/issues/10231
-
Paginating an already fetched set of data - Apollo Client/Server
There were some caching issues, outlined here https://github.com/apollographql/apollo-client/issues/6916 to be aware of
-
The Case for C# and .NET
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...
-
A high-level overview of Concurrent React
[※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]
What are some alternatives?
zustand - 🐻 Bear necessities for state management in React
react-relay - Relay is a JavaScript framework for building data-driven React applications.
axios - Promise based HTTP client for the browser and node.js
urql - The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
Recoil - Recoil is an experimental state management library for React apps. It provides several capabilities that are difficult to achieve with React alone, while being compatible with the newest features of React.
sveltekit-graphql-github - Use Apollo Client with SvelteKit to Query a GraphQL API: we use the GitHub API to query our repos and learn a bit of SvelteKit along the way.
SWR - React Hooks for Data Fetching
react-query - 🤖 Powerful asynchronous state management, server-state utilities and data fetching for TS/JS, React, Solid, Svelte and Vue. [Moved to: https://github.com/TanStack/query]
react-apollo
graphql-request - Minimal GraphQL client