Conversation
|
Before going too deep on this, do we want to have side-by-side packages like option 1 in OP or try to extract layers that can be shared like option 2 in OP, akin to Payload's current agnostic core? Further, is there a place we can communicate more seamlessly than this GH PR? Discord? We have a Discord server for https://github.com/omnidotdev, and there are also Payload and TanStack Discord servers. Otherwise, discussing here is fine, might get noisy though. I think the Payload Discord server is the most logical place to discuss |
|
Philip Yong (@flipflipyong) here! I think respecting Payload's agnostic core would be great but I'm struggling to picture how we'd introduce TanStack Start directly into PayloadCMS because it is still NextJS unless we were gonna rebuild everything in TanStack Start. But I guess everything is still React after all. Probably can reuse most code. |
Thanks for your thoughts my friend. @coopbri on Discord. I just made this thread in their server: https://discord.com/channels/967097582721572934/1451778105957159002/1451778109635559496, maybe they'll be open to a channel later (they have a pattern of making |
|
Unrelated, but I’m curious about the discussion on X, but I hate X 😂 could you screenshot the discussion? because I can’t see replies without logging in. |
|
There's some discussion but here's the main post and the response leading to this PR |
|
Another one! |


What?
(WIP) Added TanStack Start, as an alternative option to Next.js
Stemmed from this discussion, including with @jmikrut, @tannerlinsley, and others: https://x.com/0xcoop/status/2001439446932304181
Began discussing this in Discord with @jmbockhorst, he also started prototyping
Why?
TanStack Start is awesome.
How?
(WIP) pending community discussion. Main options I imagine:
packages/tanstack-start, akin topackages/next, orCurrently, this is in an early discussion phase. I will update this description accordingly as we plan.