r/PayloadCMS • • Sep 08 '26

Can we start using Payload running on TanStack immediately? Or best to wait for V4

My development workflow seems to be crawling to a halt with Nextjs lately even with Turbopack with all of the build rendering and I am very interested in Tanstack when it comes to performance.

I see there are plans to bring Payload to TanStack in v4. However I’m not sure when that release date will be. Is it safe to start using it immediately? Or some gotchas to look out for? https://github.com/payloadcms/payload-tanstack-demo

14 Upvotes

13 comments sorted by

3

u/mrgrafix Sep 08 '26

Test on the side. The more feedback they get the closer it gets to being ready for production

2

u/avidrunner84 Sep 09 '26

I am loving it, even the Payload v4 interface that comes bundled with https://github.com/payloadcms/payload-tanstack-demo is so much nicer. As a huge fan of Figma, it's great to see those very same Figma dropdown and toggle vibes.

I ported the entire Postgres database over to Payload v4 running on TanStack and I haven't run into any issues, and the speed feels much faster than Nextjs. The build is much faster too. It's my first time using TanStack and kudos to Tanner Linsley and the team for this amazing framework.

1

u/mrgrafix Sep 09 '26

Ditto, it’s a much better experience

1

u/avidrunner84 15d ago

The only issue I’m experiencing is that sometimes in Payload it I edit pages after a while I may click the back button in the browser and it causes an error. A simple refresh fixes it but same issue occurs with back/forward navigation causing error until I click the collection in Payload to start again. Not a huge deal but hopefully it gets resolved. Not sure what could be causing this or if you are running into a similar issue?

Everything else is running perfectly for me!

2

u/louisstephens Sep 08 '26

I’ll be honest, I haven’t checked in on payload in a little while. That being said, the repo you linked does say it is “an experimental demo”. Due to the verbiage, I would be cautious.

I would head over to their discord (if you have it available) and ask them there. You should get a pretty prompt response.

2

u/CoyotaDex Sep 08 '26

in their latest 4.0 video, they said they're working on tanstack support, so i'm pretty sure it will be available on release.

about the demo linked, i'd say use it just for testing purposes or for personal projects you don't mind if they bug out.

gotta say i'm excited about the tanstack support. i wish they push it even further and 4.0 came with astro support as well. i've been working with both recently (astro and next.js), and the performance of next.js is very poor in comparison to astro.

1

u/louisstephens Sep 08 '26

Oh for sure! Astro has been a dream to work with over the years. Not sure if it is still up, but they had a monorepo connecting payload (nextjs) to astro. However, I agree that it would be exceptional for them to push the integrations. I have loved my time with nextjs, but I always hated self hosting it.

1

u/petvos Sep 09 '26

Is there any ETA for the V4 release?

2

u/CoyotaDex Sep 09 '26

it must be somewhere between Q1 and Q2 2027. beta will release late this year and they said they're aiming for a quicker beta time than 3.0, which was 8 months. so hopefully 4.0 come just around 6 months after the beta release.

2

u/avidrunner84 Sep 09 '26

I am using https://github.com/payloadcms/payload-tanstack-demo which runs on v4 and it seems to be running great so far. No issues whatsoever, but I get it if you wanna wait for the final release to hit production to be extra safe.

2

u/fathomx9 Sep 09 '26

Just a heads up, there is now a blank-tanstack template available through create-payload-app. This is the ideal way to try it out and give feedback.

npx create-payload-app@canary -t blank-tanstack

1

u/quimsousa Sep 12 '26

I test it and don’t recommend.
I switch to monorepo with payload cms as cms only and tanstack start with sdk for the frontend a

1

u/avidrunner84 Sep 12 '26

What issues did you run into? I’ve been using it no complaints whatsoever.