Vicary A.

This depends on #772 (React 18), I'll take some time for the website refactoring.

@soundstep Out of curiosity I tried to build a lambda myself following the official docs and was greeted with the error `The image manifest or layer media type for the...

Turns out it's unnecessary because 1. `web.js` is imported because of Deno, Node is fine. 2. Although `client` still makes no sense for manual closing, it should be a PR...

@natew The idea is that `` has a `fallback` prop for skeletons. But it does take efforts to migrate if you have a top-level skeleton component relying on the data...

@natew I would want upcoming changes to go towards a more modular design, having the core stays slim. Unfortunately the new `React.use()` API only works with suspense, so suspense has...

@vasyas The selection tree will be tapped directly from the observers, this is the same hooks to build our queries when we fetch. I aim to reduce friction as much...

@noverby There is [`castNotSkeleton` and `castNotSkeletonDeep`](https://gqty.dev/docs/client/helper-functions#castnotskeletondeep). But use with care, only when you are using both `prepare` and `suspense` in `useQuery()` will it actually skip the first skeleton render in...

@Negan1911 There are only specific combinations of options that we can safely drop the data skeleton, i.e. 1. `useQuery()` with `prepare` and `suspense` enabled 2. `useTransactionQuery()` with `suspense` enabled 3....

@Negan1911 Really appreciate it. Be prepared because in GQty we are dealing with a lot of meta-programming, proxies, recursions and cache normalization. DM me in Discord if you are that...

# What now? The current plan is to export two schema types, 1. One with optional scalars to reflect the state before fetch, and 2. Another schema without optional to...