Repository navigation
Draft TanStack Start 1.0 announcement - #1366
Conversation
|
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| 🔵 In progress View logs |
tanstack-com | 8e988bf | Oct 12 2026, 09:34 PM |
|
|
||
| I think it was around November of 2025 when AI started noticeably changing the work around Start, and by the middle of 2026 we were dealing with it everywhere. The volume of PRs and issues went up, a lot of it was drive-by stuff, generated content that someone hadn't really read or understood before sending it to us, and that takes time away from the people actually doing the work. Security has changed along with it. People are using AI to actively look for vulnerabilities, we're using it ourselves and with partners to find and fix problems, and that's becoming a normal part of maintaining this thing. It has to be. | ||
|
|
||
| But I've also been using agents to build, and watching other people use them to build with Start, and I keep coming back to the router. All that work to make the types strict, to make the APIs explicit, to give you as much freedom as possible while still being able to tell you when something doesn't fit, we did that for people. I wanted you to be able to move things around and try things and have your editor help you, without having to remember every connection in your application. An agent needs a lot of that same help, it changes a route parameter or the input to a server function and now it can find the places that no longer agree with it, and the more complicated the application gets, the more I want that feedback. It doesn't tell you whether you've built the right thing, you still have to do that part, but it gives you a way to keep making changes without guessing about all of those connections. We didn't have to redesign Router and Start around agents to get there (the design was deliberate, having it line up this well with how people are building now was a pretty happy coincidence). |
There was a problem hiding this comment.
not sure why but this sentence sounds weird to me
We didn't have to redesign Router and Start around agents to get there (the design was deliberate, having it line up this well with how people are building now was a pretty happy coincidence).
There was a problem hiding this comment.
This whole paragraph above sounds a little AI. Maybe rewrite this one?
|
|
||
| <partner-list></partner-list> | ||
|
|
||
| And to our previous partners and sponsors, you're part of this history too (support doesn't stop mattering when a sponsorship ends). |
There was a problem hiding this comment.
support doesn't stop mattering when a sponsorship ends
this sounds a bit AI
| title: TanStack Start 1.0 | ||
| published: 2026-10-10 | ||
| draft: true | ||
| excerpt: TanStack Start 1.0 is finally here, and this is the story of how we got here. |
There was a problem hiding this comment.
and this is the story of how we got here
this sounds a bit AI
|
In general, the paragraphs here are a bit long and there's not a ton of formatting breaks throughout. (maybe a select few I also think we should have a technical section to this post in particular. A "How we're different from Next.js and others" section using code or maybe even a code-focused "How things evolved" with comments at the top explaining when an API isn't the current revision so people don't get confused |
| @@ -0,0 +1,147 @@ | |||
| --- | |||
| title: TanStack Start 1.0 | |||
| published: 2026-10-10 | |||
| --- | ||
| title: TanStack Start 1.0 | ||
| published: 2026-10-10 | ||
| draft: true |
|
|
||
| ## I wanted another option | ||
|
|
||
| It was around that time I felt like the React ecosystem was really constraining its idea of what an application should look like. Next.js was making a very big bet on React Server Components, as a framework primitive and an ideology, and moving more and more toward a server-oriented model. React Router and Remix were working through their own changes. There were interesting ideas in all of this, but I wasn't really comfortable with how the conversation seemed to land on one answer for everybody. |
There was a problem hiding this comment.
maybe "ideology" is a weird word to use here, unless it's intended to be a dig at Next
70ac2a5 to
458beb6
Compare
5 participants
Adds the TanStack Start 1.0 announcement as an unpublished draft, revised from Tanner’s spoken reading. Covers Router’s origins, contributor work, framework choices, RSC, AI and Intent, and partner support. Publication details, historical partner ordering, and unverified claims remain marked with editorial TODOs.
Adds Markdown markers for current and previous partners that render the homepage’s shared PartnersGrid, including tier bands, logo sizing, analytics, and deterministic seeded ordering. PartnersGrid now accepts a status filter, defaulting to active. The production-user showcase is not included.
Validation: pnpm test (480 passed, 1 skipped, including typecheck and lint), formatting check, and visual inspection of the shared grid in the draft.