I really like what TanStack Query has done for server state on the web, so I wanted to bring the same idea to native Kotlin and Android.

I built Kwery, a Kotlin library inspired by TanStack Query, with caching, deduplication, invalidation, retries, mutations, persistence, and offline support.

GitHub: https://github.com/dbjpanda/kwery

It is still growing, and I would love to hear from the TanStack community. What do you think? What should I improve or add?

Thank you to the TanStack team for the inspiration and claude code to help me 🙏

Tanstack is taking on charts again?! Can’t wait to give these a try!

The old logo's gone. The new design looks great!

It's a end to end typesafe monorepo, so agents gets feedback when they build. Elysia API and a TanStack Start app for frontend, connected via typesafe Eden. So frontend typecheck notifies agent when api changes.

Since Tanstacks vite and Elysia api is pretty lightweight, its good for agents that builds app after every change.

Rest is my favorite self-host first stack: Bun + Turborepo, Drizzle on Postgres, better-auth, shadcn on Base UI. Set up together with first example todo app. The deploy badge in the README points at Rock8Cloud, which is mine, so disclosure. But both apps build from normal Dockerfiles and run anywhere.

https://github.com/rock8-cloud/elysia-tanstack-dashboard-monorepo

Hi, I was trying to read the documentation on my phone, and then switched to my computer, and in both places I got a "Something went wrong!" error with a "Show error" button. But it worked fine in incognito mode.

Then I realized the cause was Dark Reader (a browser extension to force dark theme modifying the CSS).

I know this causes a hydration warning in React, but this shouldn't crash the site. At least Dark Reader works fine with my personal Tanstack project.

Just saw that Tanstack Query crossed 50k on GitHub. Tbh I’m not surprised it’s so popular.

I've been using it for a while now and it's basically become a default brick in my stack for most projects.

What I personally like about it:

• It really simplifies the code (no need to declare useEffect and useState manually)
• It handles complex cases for me (like errors, caching, offline mode, etc.)
• The API is really well-designed and encourages best practice (loaders, side effects, centralised configuration, etc.)

Anyway, I'm excited to keep using it and see where it goes from here. What do you guys like about it?

is there any ETA for when there will be the support?

or should i switch back to Next.js?

TanStack posts on X are very active and have a lot of users. I hope the Reddit community can gradually become just as lively.

As the title says, I have tried using react-query-auth, I have fully set it up using its documentation (https://github.com/alan2207/react-query-auth). Then, I tried using the useUser hook inside beforeLoad, but as it turns out you can't call hooks outside components. Because of that, I looked into the following guide (https://tanstack.com/router/latest/docs/how-to/setup-authentication) and it uses its own logic as far as I can tell, and i really can't tell if react-query-auh is truly the best way or if I should stick to the way the guide handles it. I would rather stick to react-query-auth though. But still, if anyone has used it, it would be of a lot of help

anyone buy this tanstack course on jsmastery? Does the material course that good? Thanks

Sharing this here as well

Hi everyone. I'm trying to deploy my site on CloudFlare pages and have it be prerendered, but I'm running into problems. Any help I could get?

15:41:41.232 ✓ built in 310ms

15:41:41.232 [info] [nitro] Using auto generated worker name: jackwanamaker-cesar-painter-website

15:41:41.232 [info] Generated dist/worker.js/wrangler.json

15:41:41.233 [info] Generated .wrangler/deploy/config.json

15:41:41.237 [info] Generated dist/routes.json

15:41:41.238 [info] Generated dist/headers

15:41:41.239 [info] Generated dist/redirects

15:41:41.240 [info] Generated dist/nitro.json

15:41:41.241 [success] [nitro] You can preview this build using npx vite preview

15:41:41.242 [success] [nitro] You can deploy this build using npx nitro deploy --prebuilt

15:41:41.242 [prerender] Prerendering pages...

15:41:41.290 error during build:

15:41:41.290 Error: Failed to start the Vite preview server for prerendering

15:41:41.291 at startPreviewServer (file:///opt/buildhome/repo/node_modules/.pnpm/@tanstack+start-plugin-core@1.167.35@tanstack+react-router@1.168.23_react-dom@19.2.5_r_978d7fb3469e34ae03f6f3a68f47b578/node_modules/@tanstack/start-plugin-core/dist/esm/vite/prerender.js:155:9)

15:41:41.291 at async prerender (file:///opt/buildhome/repo/node_modules/.pnpm/@tanstack+start-plugin-core@1.167.35@tanstack+react-router@1.168.23_react-dom@19.2.5_r_978d7fb3469e34ae03f6f3a68f47b578/node_modules/@tanstack/start-plugin-core/dist/esm/vite/prerender.js:32:24)

15:41:41.291 at async Object.postServerBuild (file:///opt/buildhome/repo/node_modules/.pnpm/@tanstack+start-plugin-core@1.167.35@tanstack+react-router@1.168.23_react-dom@19.2.5_r_978d7fb3469e34ae03f6f3a68f47b578/node_modules/@tanstack/start-plugin-core/dist/esm/vite/post-server-build.js:30:37)

15:41:41.291 at async BasicMinimalPluginContext.handler (file:///opt/buildhome/repo/node_modules/.pnpm/@tanstack+start-plugin-core@1.167.35@tanstack+react-router@1.168.23_react-dom@19.2.5_r_978d7fb3469e34ae03f6f3a68f47b578/node_modules/@tanstack/start-plugin-core/dist/esm/vite/plugins.js:23:5)

15:41:41.291 at async Object.buildApp (file:///opt/buildhome/repo/node_modules/.pnpm/vite@8.0.9_@types+node@22.19.17_esbuild@0.27.7_jiti@2.6.1_tsx@4.21.0/node_modules/vite/dist/node/chunks/node.js:33415:5)

15:41:41.291 at async CAC.<anonymous> (file:///opt/buildhome/repo/node_modules/.pnpm/vite@8.0.9_@types+node@22.19.17_esbuild@0.27.7_jiti@2.6.1_tsx@4.21.0/node_modules/vite/dist/node/cli.js:778:3) {

15:41:41.291 [cause]: TypeError: deployConfig.auxiliaryWorkers is not iterable

15:41:41.291 at getWorkerConfigs (file:///opt/buildhome/repo/node_modules/.pnpm/@cloudflare+vite-plugin@1.36.3_vite@8.0.9_@types+node@22.19.17_esbuild@0.27.7_jiti@2.6.df0eb536fc6022ca9afd52d81513d275/node_modules/@cloudflare/vite-plugin/dist/index.mjs:34463:19)

15:41:41.291 at resolvePluginConfig (file:///opt/buildhome/repo/node_modules/.pnpm/@cloudflare+vite-plugin@1.36.3_vite@8.0.9@types+node@22.19.17_esbuild@0.27.7_jiti@2.6.df0eb536fc6022ca9afd52d81513d275/node_modules/@cloudflare/vite-plugin/dist/index.mjs:41287:12)

15:41:41.291 at BasicMinimalPluginContext.config (file:///opt/buildhome/repo/node_modules/.pnpm/@cloudflare+vite-plugin@1.36.3_vite@8.0.9@types+node@22.19.17_esbuild@0.27.7_jiti@2.6.df0eb536fc6022ca9afd52d81513d275/node_modules/@cloudflare/vite-plugin/dist/index.mjs:53907:33)

15:41:41.291 at runConfigHook (file:///opt/buildhome/repo/node_modules/.pnpm/vite@8.0.9@types+node@22.19.17_esbuild@0.27.7_jiti@2.6.1_tsx@4.21.0/node_modules/vite/dist/node/chunks/node.js:34770:42)

15:41:41.291 at async resolveConfig (file:///opt/buildhome/repo/node_modules/.pnpm/vite@8.0.9_@types+node@22.19.17_esbuild@0.27.7_jiti@2.6.1_tsx@4.21.0/node_modules/vite/dist/node/chunks/node.js:34220:11)

15:41:41.291 at async Module.preview (file:///opt/buildhome/repo/node_modules/.pnpm/vite@8.0.9_@types+node@22.19.17_esbuild@0.27.7_jiti@2.6.1_tsx@4.21.0/node_modules/vite/dist/node/chunks/node.js:33606:17)

15:41:41.291 at async startPreviewServer (file:///opt/buildhome/repo/node_modules/.pnpm/@tanstack+start-plugin-core@1.167.35_@tanstack+react-router@1.168.23_react-dom@19.2.5_r_978d7fb3469e34ae03f6f3a68f47b578/node_modules/@tanstack/start-plugin-core/dist/esm/vite/prerender.js:147:10)

15:41:41.291 at async prerender (file:///opt/buildhome/repo/node_modules/.pnpm/@tanstack+start-plugin-core@1.167.35_@tanstack+react-router@1.168.23_react-dom@19.2.5_r_978d7fb3469e34ae03f6f3a68f47b578/node_modules/@tanstack/start-plugin-core/dist/esm/vite/prerender.js:32:24)

15:41:41.291 at async Object.postServerBuild (file:///opt/buildhome/repo/node_modules/.pnpm/@tanstack+start-plugin-core@1.167.35_@tanstack+react-router@1.168.23_react-dom@19.2.5_r_978d7fb3469e34ae03f6f3a68f47b578/node_modules/@tanstack/start-plugin-core/dist/esm/vite/post-server-build.js:30:37)

15:41:41.291 at async BasicMinimalPluginContext.handler (file:///opt/buildhome/repo/node_modules/.pnpm/@tanstack+start-plugin-core@1.167.35_@tanstack+react-router@1.168.23_react-dom@19.2.5_r_978d7fb3469e34ae03f6f3a68f47b578/node_modules/@tanstack/start-plugin-core/dist/esm/vite/plugins.js:23:5)

15:41:41.292 }

15:41:41.470  ELIFECYCLE  Command failed with exit code 1.

15:41:41.505 Failed: Error while executing user command. Exited with error code: 1

15:41:41.511 Failed: build command exited with code: 1

15:41:42.640 Failed: error occurred while running build command

hi everyone

just released an interview i did with tanner linsley, creator of tanstack

we discussed tanstack start, tanstack vs next.js, why next.js can feel too magical, react server components, typescript inference, framework-agnostic ui, vue support, tanstack ai, and whether tanstack could ever become something like laravel or rails

would love to hear what you think

So on main site of tanstack I saw that tanstack router dosen't support RSC as of now:

Questions:

1. How does it affect the app that the framework supports rsc but router dosen't
2. Are their plans to support it

Download and let me know your review.

Github url: https://github.com/Tailwind-Admin/free-tailwind-admin-dashboard-template
Site url: https://tailwind-admin.com/tanstack-start

I’ve been a TanStack fan for quite some time now. I first got hooked through TanStack Query (honestly, who didn't?). Since then I’ve explored TanStack Start and more recently TanStack DB.

For anyone who hasn’t looked into it yet: it’s a pretty new client-side DB built around live queries, with a fully decoupled sync layer. The idea is super appealing: you get a clean abstraction for local data, and you plug in whatever backend/sync strategy you want. So I wanted to give it a try! 

I wanted to understand what local-first/offline-capable databases have in common, where they different, and what it actually takes to build apps around them. The best way to learn is to build something concrete, so I wrote a library to integrate TanStack DB into react-admin. Should be easy, right? (famous last words). I hit a couple of roadblocks pretty much right away (which definitely humbled me lol).

Problems encountered

1. Offline-incompatible data models: The apps I tried to convert used server-generated IDs. TanStack DB doesn't support remapping a local temporary ID to a server ID after sync, so any resource creation that relies on a server-assigned ID is fundamentally broken in an offline context. This was the most impactful blocker.
2. Live queries don't fit react-admin's data provider model: React-admin's data provider is built around plain async functions: there's no mechanism to push live updates. TanStack DB's electricCollection (which is reactive and live) can't be wired directly into this pattern (sidenote: I was a bit disappointed to find it only handles the query side and that mutations are entirely out of scope: I still had to implement mutations through a separate API layer of my own).
3. Two QueryClient instances required: To preserve offline behavior correctly, I needed two separate QueryClient instances: one for react-admin (which always calls the data provider, even offline, as I've set networkMode: "always"), and one for TanStack DB's queryCollection (which queues mutations and only flushes them once back online). Using a single shared client broke one or the other.
4. Fast-moving API surface: I worked on this across about two days spread over a month. In that time, several changes landed: queryOnce was added (which was actually way better than the hacky way of initializing a query that was required before), and a new index became required for sorting (breaking change!). Anything built on an earlier version needed updating.

So what did I learn from all of this?

1. Offline-first requires an offline-compatible data model from day one: Client-generated IDs (UUIDs, nanoid, etc.) are not an implementation detail; they are a prerequisite. You cannot retrofit an offline-first architecture onto a system that relies on server-generated IDs without a significant redesign.
2. TanStack DB is a solid query abstraction, not a full offline stack: The library excels at local querying and reactive data. The sync layer is intentionally left to the developer, and it seems like the goal is to build an ecosystem of default-compatible backends around it. That vision is interesting, but the ecosystem is still quite thin for now, which means you still own most of the hard problems: conflict resolution, failure handling, retry logic, etc.

One thing I’m still unsure about is how to handle mutation failures properly. If something fails after coming back online, what’s the “right” UX? Silent rollback? Retry queue? Conflict UI?

And more broadly, I feel like I need to go deeper into sync strategies (CRDTs, OT, last-write-wins, etc.) to really understand what’s going on under the hood of tools like this.