GQty

A No-GraphQL client for TypeScript.

[GQty @g_qty]

When you need fast iterations, don't let your API gets in the way.

[Deno @deno_land]

Help us spread the word — it's time to #FreeJavaScript.

https://t.co/H5MqGRawAq

[GQty @g_qty]

@SirSeanOfLoxley @natebirdman @thdxr Thats exactly what prepare does! It also skips the first render for Suspense.

[GQty @g_qty]

@alvarlagerlof @natebirdman If a field accepts arguments, it becomes a function.

[GQty @g_qty]

@natebirdman @takezeasy @devagrawal09 @TkDodo @DorShinar You make GraphQL selections via our Proxy, we suspense and fetch the combined query in the next microtask.

[GQty @g_qty]

@natebirdman @en_JS @jamonholmgren @coolsoftwaredev @frankcalise @poteto @SashaRakovets It's a new Proxy on every read, supporting React Compiler should be trivial.

[GQty @g_qty]

@fernandorojo @natebirdman Because introspection said so!

[GQty @g_qty]

When you need fast iterations, don't let your API gets in the way.

[GQty @g_qty]

@mirshko This is exactly what keeps us going!

[mirshko @mirshko]

@g_qty I am blown away by the quality of life improvement y'all bring! God damn!!!

https://t.co/y8jObQ2VSk

[GQty @g_qty]

Huge shoutout to @graphapi_io for picking us as the best GraphQL client 🤩

https://t.co/qUC4RT1QaG

[GQty @g_qty]

❎ Your third favourite GraphQL tools
✅ Your first favourite GraphQL client

[Jamie Barton 🥕 @notrab]

3️⃣ GQTY: A No-GraphQL client for TypeScript.

If writing GraphQL operations and configuring codegen for TypeScript is slowing you down, consider replacing your GraphQL client with no GraphQL client and using @g_qty instead.

https://t.co/P0ecJjjEAf

[Expo @expo]

Stoked to share some announcement highlights from our first day of talks at the 2023 @appjsconf . You can re-watch them all (and catch day 2, which starts in ~8 hrs) on @swmansion's YouTube channel!

[GQty @g_qty]

@supabase You deserve a shoutout!

pg_graphql is actually dope, our users are starting projects in a minute or two!

[Step CI @ci_step]

We just released Garph 0.5 🙌

Garph enables you to build e2e type-safe GraphQL APIs using TypeScript.

https://t.co/MpasJILayU

[GQty @g_qty]

@fireship_dev Roast me daddy.

[GQty @g_qty]

It means our core API works with Server Actions since day 0 🤯

[JLarky @JLarky]

RSCs mutation api leaked?

[GQty @g_qty]

Query batching in RSC just works, who would have known? 🤯

[GQty @g_qty]

In GQty, we eat meta programming for breakfast!

[📦🛠👷🏻‍♂️Sean Larkin @TheLarkInn]

Intro into the Dark Arts:

[GQty @g_qty]

@bronifty @Jeansse It wasn't really decided until now. "Gee, cutie" sounds so funny, I added the pronunciation next to our logo in https://t.co/4ikY8WWnKf!

[GQty @g_qty]

Our optimistic updates are simple value assignments.

[Nate @natebirdman]

I think it’s smart to pay attention to what makes RPC popular - simplicity. It’s why Garph and others look interesting as well. Combined with @g_qty i think you get even better DX than any RPC, but also get amazing performance.

In the original now defunct @gqlessdev they had mutations where you just mutate the object directly which is beautiful.

That level of DX will win long term imo. Just needs more investment. The gqty site is being remade as it needs it desperately

[GQty @g_qty]

Inspired by the amazing refetches in TanStack Query, our new major also gives you soft refetches that skips network on a fresh cache, on window focus, on interval and on each render.

You can literally start trying GQty in 10 secs, greenfield or brownfield.

[GQty @g_qty]

Imagine rendering off the cache like the data is already there. Whenever you reach a scalar, we mark that in our pending query, and we combine and fetch all of them in the next tick.

So you have data colocation, query batching and fragments in one go.

Minus the learning curve.

[Jens Neuse | Founder @ WunderGraph @TheWorstFounder]

A lot of devs these days are drawn towards RPC frameworks. When you ask them about their opinion on GraphQL, they usually think it's too complicated and too much overhead. When you ask them about Fragments, decoupled Components, Data masking, they usually don't even know what these concepts are.

So here's my prediction for the future. We will drive further into the RPC direction for a while until this cohort understands the drawbacks of RPC and REST compared to GraphQL.

Meanwhile more and more tooling will make the adoption of GraphQL, Relay and co easier and the whole ecosystem even more powerful.

At some point, this cohort will come back to GraphQL, realizing that the "overhead" is the price for making your frontend scalable.

This whole RPC story is super strong when all you have is a single NextJS app and you can keep everything in one single repository. But even at this stage, you'll already run into the limitations of not having "Fragments".

Once you scale beyond that one NextJS app, you really want to have a query style API with a client like Relay.

[GQty @g_qty]

If you don't like the double rendering in Apollo, turn on Suspense and we have you covered.