SvelteQuery vs KitQL vs others

This page summarizes the projects mentioned and recommended in the original post on /r/sveltejs

Our great sponsors
  • SurveyJS - Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • graphql-request

    Minimal GraphQL client

  • What about https://github.com/prisma-labs/graphql-request that has 4.8k starts / 254 forks?

  • TanStack Query

    🤖 Powerful asynchronous state management, server-state utilities and data fetching for the web. TS/JS, React Query, Solid Query, Svelte Query and Vue Query.

  • SvelteQuery is in the coming soon stage (no idea if this is the same as under development, but I do not think so) - https://tanstack.com/query

  • SurveyJS

    Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

    SurveyJS logo
  • gQuery

    Not like jQuery. A GraphQL Fetcher & Cache for Svelte Kit

  • Check out https://github.com/leveluptuts/gQuery too. This is what we use on Level Up Tutorials and it couldn't be easier.

  • houdini

    The disappearing GraphQL client (by HoudiniGraphql)

  • Full disclosure: I'm the author of KitQL & maintainer of Houdini I've been in the GraphQL ecosystem for a long time and love it. I discovered Svelte early 3.0 and directly opt-in SvelteKit at the very beginning. I've tried different approaches with codegen Apollo & urql. Helping developing graphql-codegen-svelte-apollo at first then urql-svelte-operations-store. Contributing / creating / maintaining open source is something I like to do to build a friendly community around similar stacks. Then gQuery came out and took a radical new approach to things in a great way. I was hyped about it, especially for the simplicity and SSR out of the box. I believe that multiple projects bring new ideas to the community, which is awesome. It's here that I created KitQL to unlock some options that I need for my customers (Yes, I don't do only open source ^^). My aim with KitQL is to focus on two things: 1/ Embrace the community. To build something with others that satisfies many use cases. 2/ Build a full stack GraphQL on SvelteKit. Client + Server, using all powerful tools from The Guild. Thx to the community; we get to speak with amazing people, and I got the chance to talk with the Houdini author. After a few conversations, we decided to join forces. KitQL Client had a few issues that will be complicated to solve: no normalized cache, prefetch cannot work, leaks in SSR... to name a few. So I deleted KitQL Client in favor of using Houdini. KitQL is now focused on the backend part and module development (but it's not the topic here). Houdini has significantly evolved in the last months to bring KitQL flow inside + keep all its benefits! I think that it has a unique DX matching a lot of different styles of programming. You want your GraphQL operations in a separate file? Inside your Svelte componennt? You want Houdini to generate some boilerplate to focus only on your business logic? You want Houdini to create magic fragments to insert into a list automatically after a mutation? Houdini got you covered! And you know what? With the new '+page.svelte' directory structure, Houdini will go to another level!!! In a few days, we will merge a PR that will improve even more the DX and will be sooo integrated with the new SvelteKit changes. //I'm so excited about it. Come and check #BuildInPublic https://github.com/HoudiniGraphQL/houdini As you could read, the most important is the community, so thank you!

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts