graphql-typed-document-node
react-query
graphql-typed-document-node | react-query | |
---|---|---|
7 | 190 | |
370 | 27,869 | |
- | - | |
3.9 | 9.1 | |
4 months ago | almost 2 years ago | |
TypeScript | TypeScript, JS | |
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.
graphql-typed-document-node
-
how to correctly specify query variable when generating TS types from graphql-typed-document-node?
When using graphql-typed-document-node to generate TS types from gql, I am getting errors when my query has variables.
-
Show HN: Typed GQL in Zeus 5.1.5
https://github.com/dotansimha/graphql-typed-document-node
Big thanks to Dotan Simha for creating this TypedDocumentNode!
-
Typed GraphQL with react-query & graphql-request
GraphQL Code Generator can generate fully typed React hooks if you tell it to, but I'm a fan of keeping things simple and thereby of their TypedDocumentNode approach. This variant is unaware of the GraphQL client that you're using. In other words, it's not tied to react-apollo (or alternative).
-
Typed document node with apollo v4 and laravel lighthouse complex where
Hi, I use this package https://github.com/dotansimha/graphql-typed-document-node and I usually call it like this useQuery(peopleDocument, variables).
-
The Next Evolution of GraphQL Front Ends
Controllers are great for lots of reasons. One reason we've found while developing and testing Apollo Elements is that unlike the class-based API of e.g. @apollo-elements/lit-apollo or @apollo-elements/mixins, when using controllers there's no need to pass in type parameters to the host class. By passing a TypedDocumentNode object as the argument to the controller, you'll get that typechecking and autocomplete you know and love in your class template and methods, without awkward class generics.
-
TypedDocumentNode: the next generation of GraphQL and TypeScript
So today, after successfully integrating this feature into few of our largest clients, we can proudly share it with you - TypedDocumentNode.
-
GraphQL - Diving Deep
Want to generate Typescript objects based on GQL documents? You can try out Typed Document Node
react-query
-
20 Essential Parts Of Any Large Scale React App
react-query
-
Some Very Cool (Underrated maybe) React Libraries
React Query: This library makes it easy to manage data in your React applications, from fetching to caching and updating data. It offers a simple, powerful, and flexible API for handling data and keeping your UI in sync with your data. https://github.com/tannerlinsley/react-query
-
Do I need a fetching library in React?
useQuery (react-query) (+) all from above (+) even more features (-) more complex, even the examples are complex, has more aggressive defaults (re-fetching every 2s)
-
Is there any redux-saga equivalent for zustand?
see here Overview
-
React Query Codegen from OpenAPI
Rapini is a new tool that can generate custom React Query hooks using OpenAPI (Swagger) files.
-
React hooks for 28 RxJS operators
React Query is the gold standard for using async data declaratively with hooks. I ended up needing to modify even my simple useTimer hook to work more like useQuery to take multiple keys in order to work as an inner observable for other operators.
-
Goodbye, useEffect - Reactathon 2022
For most situations, I would recommend using a library like React Query. It handles a lot of common data-fetching boiler plate and already accounts for this useEffect() issue. Also, it supports Suspense if you want to use that.
-
Managing application cache with react-query, and code generation.
At this point, I want to move on to the react-query cache management library. Give a brief overview and see how you can improve your developer experience with cache using this library.
-
When to use a hook, and when to use a service?
There isn't the "service" concept in React. If you need to send off data you can just do so with fetch. If you need to load data and cache it so it can be used across components and unmounts, then something like react-query is what I'd recommend. But it's basically a combination of React Context, useEffect, and useState to manage the cache and lifecycle of a request.
-
What would you consider to be a must for a modern 2022 dev stack?
react-query is pretty neat too. I default to that for most projects unless it's something unusual
What are some alternatives?
graphql-let - A webpack loader / babel-plugin / babel-plugin-macros / CLI / generated file manager of GraphQL code generator.
SWR - React Hooks for Data Fetching
graphql-code-generator - A tool for generating code based on a GraphQL schema and GraphQL operations (query/mutation/subscription), with flexible support for custom plugins.
axios - Promise based HTTP client for the browser and node.js
graphql-request - Minimal GraphQL client
redux-saga - An alternative side effect model for Redux apps
TypeGraphQL - Create GraphQL schema and resolvers with TypeScript, using classes and decorators!
rtk-query - Data fetching and caching addon for Redux Toolkit
react-relay - Relay is a JavaScript framework for building data-driven React applications.
zustand - 🐻 Bear necessities for state management in React
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.