Problem: I want to show a spinner if any React Query mutations are in progress.

Solution: useIsMutating. This hook returns true if any mutations are running.

Problem: I want to show multiple spinners, depending on which mutations are pending.

Solution: useMutationState. This

Tiger Abrodi tRPC.io 🧙‍♂️ Dominik 🔮 Alex / KATT 🐱 Because streaming the resulting html every request != streaming the js once and then only the data every request. There will always been an inflection point where one is more attractive for your applications performance/interactions than the other. Component dynamism,

My timeline is full of effect today 😊

Are you excited about Effect?

How does TypeScript module augmentation work in a monorepo with a composite setup? We have one package A that augments a 3rd party definition (@tan_stack router in this case), but how would package B 'see' that augmentation if A already depends on B 🤔

What am I reading here? I'm so confused 🙃

🔮 Exciting news: I'm so happy to announce that the course on TanStack Query I've been working on will launch May 22 🚀

Huge thanks to Tyler McGinnis and the team behind ui.dev for working with me on this 🙏

🚢shipped it:
github.com/TanStack/query…

I think I'm ready to ship the scoped mutations feature. Here's the PR if you want to give it a look: github.com/TanStack/query…

It refactors a lot in our internal logic, which is also used in queries. Wouldn't be possible without the extensive test coverage. Still a bit scary 😅

My 2 big (technological) bets for this decade:

1) Local-first: A different way how apps are architected – mainly how data flows and responsibility of client vs server.

2) Effect: A better foundation to build with TypeScript.

If an interviewer asks me 'Which is more performant: .forEach() or a for/of loop?' I walk out of the door and never come back.

esm / cjs is still a living hell and I see no way out of it for lib maintainers any time soon 😩

I wrote this over a year ago, and I still believe it's 100% true. React isn't dying.

tkdodo.eu/blog/why-react…

Based on Dominik 🔮's article, here's how to create a reusable 'createZustandContext' function.

Just a sprinkling of generics, a bit of knowledge about Zustand's 'StoreApi' type, and you're good to go.

📜 Zustand and React Context - Dominik 🔮

You'd get great benefits by putting your Zustand store in a React context:
- init store from props
- improved testability
- multiple local instances

100% agree with this article

twitter.com/TkDodo/status/…

Trust me that there's no unwarranted shill when I say that I've never seen tech education quality quite like this new Query course. The ui.dev team are geniuses and Dominik 🔮 is quite literally our planet's leading expert on all things Query.

If you want to learn Query, this is

100% agree

To me, NOT putting your Zustand store in a React context almost feels like an anti-pattern

You should be able to test things easily and write that:
<>
<ProvideZStore><Item1></ProvideZStore>
<ProvideZStore><Item2></ProvideZStore>
</>