Post

LinkedIn must be right I guess. Time flies. Oh, and we’re working on @tanstack.com Query v6. I’ll post a public roadmap soon. Coincidence ? I think not 😄

Randy Northrup

@randynorthrup.bsky.social

Looking forward to the roadmap. Is v6 mostly API cleanup, or are bigger changes coming to how the cache and suspense work together?

Dominik 🔮

@tkdodo.eu

current things are mostly cleanup and internal rewrites for better hydration. Suspense is a beast 😅

8/10/26, 9:09 am0 reposts2 likes

sugoyona.bsky.social

@sugoyona.bsky.social

Suspense hydration issues are always tricky to clean up.

Randy Northrup

@randynorthrup.bsky.social

Especially with streaming, where the data can arrive before the component that needs it. Ordering bugs that only show up on slow networks are the worst kind.

Randy Northrup

@randynorthrup.bsky.social

Hydration is where the strangest bugs live, so internal rewrites there are worth more than new API surface. Good luck taming it.

Fredrik Höglund

@ephem.dev

Sure is. When I wrote the original hydration APIs, we didn't have concurrency, Server Components, streaming data hydration etc to deal with. Support for those have kinda been tacked on as we've explored how to make each thing work, now it's time to go back and fix some of the core stuff.

Fredrik Höglund

@ephem.dev

I guess one might argue it's been time for a while, and I wouldn't disagree, but life happens and time flies. 😅

Randy Northrup

@randynorthrup.bsky.social

Seven years of an API holding up through concurrency, RSC and streaming is a good run. Fixing the core once you know the real shape of the problem is the right order anyway.

Dominik 🔮

@tkdodo.eu

Great stuff for a talk btw how things being designed 7 years ago are still used but don't necessarily support modern patterns and need re-thinking 💡

🫡

@ephem.dev is on it 🔥

Randy Northrup

@randynorthrup.bsky.social

Good hands, then. Looking forward to the v6 roadmap.