👋 Who we are

urql is a customizable and versatile GraphQL JS Client that has seen a steady growth in popularity over the years as a major contender in the space and has developed into an independent community, maintained and governed by volunteers and our core team. We believe in the growth and success of GraphQL and support our community in achieving their goals and working on their projects with urql.

We believe in building pragmatic, intuitive and performant APIs, and our guiding principles are to:

• Develop from first principles.
• Stay Unopinionated & Flexible.
• Build Intuitive, Extensible APIs.

👋 What we build

To date, urql supports the Preact, React, Svelte, and Vue communities via our library bindings, and are covering all major features that are required and expected from a GraphQL client.
Furthermore, urql supports a range of first-party exchanges, which are extensions providing core functionality, such as authentication mechanisms, normalised caching, debugging, and more.

We also currently maintain sibling projects to urql, which are separate, since they don't depend on or aren't directly related to it, but are independently built to be reusable by the entire GraphQL ecosystem.
These are hosted on the 0No Co organization and include:

• Wonka — The Push/Pull streaming library that powers urql
• graphql.web — A spec-compliant minimal GraphQL implementation for the client-side
• graphql-web-lite — An aliasable drop-in replacement for the graphql package for the client-side
• gql.tada — A typed-document library for GraphQL query authoring in TypeScript
• graphqlsp — A TS language server plugin for GraphQL and gql.tada

💕 Why your support matters to us

Your support means urql and our other projects will remain sustainable and compensate our core team and active contributors. Our goal is to sustain and further our work in the GraphQL and Developer Experience space as part of the urql project in the future.

A lot of our time will go towards answering any questions — from helping more people find urql, learn how to use it, and contribute back to the community by sharing their problems, to working on larger projects that will make urql accessible and usable to more teams.

Our most recent research work has gone towards "urql as a framework" and we're looking ot be able to spend more time on building solutions that remove friction for developers and teams favouring any UI library of their choice to work together and build GraphQL applications more efficiently.