urql-graphql /urql
The highly customizable and versatile GraphQL client with which you add on features like normalized caching as you grow.
★ 8,983⑂ 483👁 82⑃ 1,664● 1,008▤ 662
-1
日增长
8,983
stars
483
forks
82
watchers
1,664
prs
1,008
issues
662
releases
README
A highly customisable and versatile GraphQL client
✨ Features
- 📦 One package to get a working GraphQL client in React, Preact, Vue, Solid and Svelte
- ⚙️ Fully customisable behaviour via "exchanges"
- 🗂 Logical but simple default behaviour and document caching
- 🌱 Normalized caching via @urql/exchange-graphcache
- 🔬 Easy debugging with the urql devtools browser extensions
urql is a GraphQL client that exposes a set of helpers for several frameworks. It's built to be highly customisable and versatile so
you can take it from getting started with your first GraphQL project all the way to building complex apps and experimenting with GraphQL clients.
📃 For more information, check out the docs.
💙 Sponsors
BigCommerce
WunderGraph
The Guild
BeatGig
🙌 Contributing
The urql project was founded by Formidable and is actively developed
by the urql GraphQL team.
If you'd like to get involved, check out our Contributor's guide.
📦 Releases
All new releases and updates are listed on GitHub with full changelogs. Each package in this
repository further contains an independent CHANGELOG.md file with the historical changelog, for
instance, here’s @urql/core’s
changelog.
If you’re upgrading to v4, check out our migration guide, posted as an
issue.
New releases are prepared using
changesets,
which are changelog entries added to each PR, and we have “Version Packages” PRs that once merged
will release new versions of urql packages. You can use @canary releases from npm if you’d
like to get a preview of the merged changes.
📃 Documentation
The documentation contains everything you need to know about urql, and contains several sections in order of importance
when you first get started:
- Basics — contains the "Getting Started" guide and all you need to know when first using urql.
- Architecture — explains how urql functions and is built.
- Advanced — covers more uncommon use-cases and things you don't immediately need when getting started.
- Graphcache — documents "Normalized Caching" support which enables more complex apps and use-cases.
- API — the API documentation for each individual package.
Furthermore, all APIs and packages are self-documented using TSDocs. If you’re using a language
server for TypeScript, the documentation for each API should pop up in your editor when hovering
urql’s code and APIs.
_You can find the raw markdown files inside this repository's docs folder._Top issues
#1062RFC: Cross-Tab Synchronization Exchange11 comments · 2020-10-14#1408RFC: Fragment Suspense boundaries in React bindings10 comments · 2021-02-22#3073RFC: Add a way to minify query before sending it9 comments · 2023-03-17#3801Add custom URQL exchange to handle aborted operations via AbortSignal8 comments · 2025-07-17#2713RFC (graphcache): Cache resolve & invalidate with partial args6 comments · 2022-10-04#2558RFC: Add stricter types for `cache` in graphcache resolvers6 comments · 2022-07-22#3618Cache update and invalidation in same transaction voids the update5 comments · 2024-06-18#3538RFC: Graphcache strong typing3 comments · 2024-03-19
Discussions
#3917SolidJS 2 compatibility for @urql/solid1 comments · 2026-10-17#3891@urql/svelte - migrate from stores to Runes0 comments · 2026-06-15#3872how to upload image use @urql/vue1 comments · 2026-05-21#3870GraphCache"updates" mutation updater not being called1 comments · 2026-05-13#3867Is it possible to have a completely offline Web app?1 comments · 2026-05-01#3863Is a `<Suspense />` boundary optional on suspense-enabled queries in `@urql/next`?1 comments · 2026-04-03#3854Shouldn't graphcache 9 detect and delete old cached data?1 comments · 2026-02-26#3835Disabling partial responses but schema awareness1 comments · 2025-12-31
Latest release
@urql/[email protected] @urql/[email protected] 2026-10-02Patch Changes - Defer requests that subscription results cause for queries that already have a request in flight. Previously, a burst of subscription events updating a slow query could send a duplicate request for every other event. The query is now refetched once, after its in-flight request completes Submitted by @JoviDeCroock (See 3912) - Mark cached results of queries as stale while a network request for them is in flight. Previously, when a mutation updated a network-only query while its request was in flight, the query's cached result looked final, so toPromise() resolved with it befo