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 😄

7/10/26, 9:21 am0 reposts48 likes

sugoyona.bsky.social

@sugoyona.bsky.social

Query v6 roadmap sounds great. Looking forward to seeing what is coming.

@yoyoyoyo.bsky.social

But I just migrated to use query options in a ton of repos. :D Am I going to be ok?

Dominik 🔮

@tkdodo.eu

Yes, we're not gonna change much :) I'll post the public roadmap as soon as we have it.

@yoyoyoyo.bsky.social

Alexander Karan

@alexanderkaran.bsky.social

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 😅

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.

Dominik 🔮

@tkdodo.eu

@ephem.dev is on it 🔥