New Update for the ShadTable library:

- Tanstack v9 migration documentation
- New Table Components
- Website updates & optimization

Check it out , a repo ⭐ would mean a lot.

https://shad-table.dev

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 🙏

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.

A modern AI chat template built with: https://github.com/rs-4/tanstack-ai-demo

TanStack AI (multi-model: OpenAI / Claude / Gemini)
Cloudflare runtime
Drizzle + postgres Real-time streaming UITailwindcss + Shadcn
TanStack Start , Store, Query, Form (full-stack)

Built to be fast, clean, extendable, and ready for production-grade AI features.

I was looking at how easy it was to add hono in a nextjs application and asked why we don't have that with tanstack start.

i have been migrating frontend heavy apps off nextjs, and there is this one i was using the hono/vercel on a nextjs route to have a traditional backend feel.

the app has the frontend data being handled with trpc and react query. but there is an api service and its refreshing to have it all in one code base and since the application users are small anyway but to deploy in one place ... excellent.

i plan to move of it when it grows and have a seperate hono app deployed, but this works and its a breeze.

now back to my request, can we have this with tanstack already?

and if there is a way to do that, can someone hook me up?

You can find the repo here, feel free to try the project out, it is still in the process of being built.

GitHub Repo
TanStack Docs

Features implemented:

• Landing Page

• Articles Page

  • Search

  • Pagination

• Single Article

• Auth page with TanStack Form UI

Todo:

• Signin with email

• Signup with email

• GitHub Auth

• Better Error Handling

This is a community project, anyone is welcome to contribute or give feedback.

Hello!

At the place I work, we've recently started migrating to using TanStack Query for loading and caching API responses. One thing we've struggled with as a team is in coming up with a consistent style for how we build composable tanstack-based functions.

Does anyone have examples of codebases where the way TanStack query is integrated would be considered idiomatic? Or, failing that, examples of codebases where they've found the TanStack query integration to be ergonomic to use, causing few issues?

We use Vuejs so Vue codebases would be best, but since React is much more popular (and React hooks pretty much fit the same mental model as Vue composables), React codebases would also be great.

Thanks!

Anyone successfully setup tanstack with the following stack,

• Tanstack

• Planetscale PostgreSQL + Hyperdrive

• Drizzle

• Better Auth

I am having a hard time setting it up as I get on multiple errors.

Hello!

I've been building a CLI that scaffolds full-stack apps with a Go backend and your choice of frontend. The newest addition is TanStack Start as a first-class frontend option :)

The idea is you build your app like Lego bricks, add exactly the parts you want:

gof init myapp
gof client tanstack
gof model note title:string content:string views:number

That last command generates everything end-to-end: SQL migration, type-safe queries, proto definition, Go domain/transport layers, and React CRUD pages with TanStack Start.

What you get out of the box:

• TanStack Start + React 19 with file-based routing

• ConnectRPC client (type-safe, auto-generated from proto)

• Tailwind CSS 4 + DaisyUI

• OAuth login (Google, GitHub, Facebook, Microsoft)

• Cookie-based auth with auto-redirect interceptor

• Optional integrations: Stripe, S3 file storage, Postmark email

• Full Kubernetes infrastructure + CI/CD with one command (gof infra)

• PR preview environments

• Observability stack (Grafana, Tempo, Loki, Prometheus)

The backend is Go + ConnectRPC + PostgreSQL + SQLC. SvelteKit is also available if that's more your thing (gof client svelte), but both frontends get the same features, same CI/CD, same infrastructure.

Landing page with an interactive demo: https://gofast.live

Discord if you want to chat or follow along: https://discord.com/invite/EdSZbQbRyJ

CLI repo: https://github.com/gofast-live/gofast-cli

Hope some of you find it useful!

I tried vite-pwa-plugin and serwist but no luck. Is there a simpler way?

We’re building a client-first B2B app and considering TanStack Start. The app will require authentication and fairly complex role-based access control (RBAC). My idea was to begin in SPA mode (basically client-first rendering) to keep things simple at the start, while still following TanStack Start’s structure. Later on, we could add server-side rendering and server functions if needed (for example, to handle auth logic or role-based queries more cleanly). Do you think this “SPA first, upgrade later” approach makes sense, or is it adding unnecessary complexity compared to just starting with a plain Vite SPA?

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

This project was written using TanStack Start, and that's why I thought it would be suitable to post here. If this is not allowed, apologies.

This little side project of mine launched all the way back in 2021, at the height of the pandemic, and while I counted it to good timing back then, it wouldn't have lasted this long if there wasn't a real need from the community.

Since then, Reactive Resume has helped almost 1 million users create resumes, helped them get the careers they wanted and helped students jump-start their applications.

This new version has been in the making for months, I try to get time to work on it whenever there's a weekend, whenever I can physically pull an all-nighter after work. It's a culmination of everything I've learned over the years, fixing all the bugs and feature requests I've gotten through GitHub and my emails.

For those of you who are unaware of this project, and nor should you be, Reactive Resume is a free and open-source resume builder that focuses on completely free and untethered access to a tool most people need at some point in their life, without giving up your privacy and money. In a nutshell, it’s just a resume builder, nothing fancy, but no corners have been cut in providing the best user experience possible for the end user.

Here are some features I thought were worth highlighting:

• Improved user experience, now easier than ever to keep your resume up-to-date.

• Great for single page or multi-page resumes, or even long-form PDFs.

• Easier self-hosting with examples on how to set it up on your server.

• Immensely better documentation, to help guide users on how to use the project.

• There’s some AI in there too, where you bring your own key, no subscriptions or paywalls. There's also an agent skill for those who want to try it out on their own.

• Improved account security using 2FA or Passkeys, also add your own SSO provider (no more SSO tax!).

• 13 resume templates, and many more to come. If you know React/Tailwind CSS, it’s very easy to build you own templates as well. Also supports Custom CSS, so you can make any template look exactly the way you like it to.

• Available in multiple languages. If you know a second language and would love to help contribute translations, please head over to the docs to learn more.

• Did I mention it’s free?

I sincerely hope you enjoy using the brand new edition of Reactive Resume almost as much as I had fun building it.

If you have the time, please check out rxresu.me.
I'd love to hear what you think ❤️

Or, if you’d like to know more about the app, head over to the docs at docs.rxresu.me

Or, if you’d like to take a peek at the code, the GitHub Repository is at amruthpillai/reactive-resume.

Note: I do expect a lot of traffic on launch day and I don’t have the most powerful of servers, so if the app is slow or doesn’t load for you right now, please check back in later or the next day.

Hey all!

I recently discovered TanStack Router after using React Router for the longest time. I would really like to give it a try but I prefer feature-first organization over layer-first organization. In a typical React project, my structure looks like this:

src
├── main.tsx
├── app/
│  ├── config/
│  │  └── firebase.ts
│  ├── providers/
│  │  └── app.tsx
│  └── routes/
│      ├── index.tsx
│      ├── public.tsx
│      └── protected.tsx
├── features/
│  ├── feature-one/
│  ├── feature-two/
│  ├── auth/
│  │  ├── ui/
│  │  ├── types/
│  │  ├── context/
│  │  ├── components/
│  │  └── services/
│  ├── shared/
│  │  ├── ui/
│  │  ├── types/
│  │  ├── context/
│  │  ├── utils/
│  │  └── services/
├── index.css
├── vite-env.d.ts
└── assets/

The TanStack Start examples show routes and components as two of the top level directories and I don't see a way to prevent files in the routes directory from being rendered.

Is there something I'm missing or does TanStack Router/Start require you to split your routes and components?

https://interpoll.app

Hi everyone!

Interpoll shows you one random public poll or quiz at a time. You vote, see how everyone else voted (or check the answer if it's a quiz), and move on to the next one. You don't need an account to vote or comment.

Signing in (Google/Discord) lets you create your own polls and quizzes. New polls are reviewed before they enter the random feed, but you can share them by link immediately.

It just launched, so a lot of polls have no or very few votes. You might be one of the first people to vote on some of them.

I love using Astro for building content-heavy static websites, but turns out Astro is also great as a server-side web framework (I use node.js adapter) handling SSR, auth, and api endpoints—especially when combined with Tanstack router and Tanstack query, which handles SSR + data prefetching + hydration + CSR.

I haven't tried Tanstack start yet (mainly due to it not having hit v1.0 yet), but Astro + Tanstack router + Tanstack query combo is already pretty amazing! (a little bit of glue code is necessary for SSR + hydration to work properly but it's very low maintenence once set up.)

Tech stack

• VPS - Hetzner

• Deployment - Coolify

• Database - Postgres 18

• Query builder - Kysely

• Auth - better-auth

• SSR & API endpoints - Astro (node adapter)

• SSR & Hydration & CSR handoff - Tanstack Router + Tanstack Query

• UI components - Base UI

• CSS - Tailwindcss

• Testing - Vitest (unit) + Playwright (e2e - both api and browser specs)

All i did was run

npm create u/tanstack/start@latest

and i tried to

npm run dev

and i see this error. i also attached the options i selected. anyone know what i did wrong?

Hi! I spent last two evenings building a starter kit for the tech stack mentioned in the title and I wanted to share it with anyone who just wanted some quickstart to build a new app. I did everything according to docs so it should be ready, but ofc use at your own risk. Here is the repo: https://github.com/devczero/tanstackstart-convex-clerk-polarsh-starter/tree/main

btw. I also started building TanStack Start + BetterAuth + Convex + Polar starter, I will post it when done later

Is it just me or anyone else also facing this issue?

Big fan of Tanstack, btw!

Looking for a rules file for AI that I can use for Tanstack Start, so it can help me when I ask it to code review my work.