Jack Herrington

Folks keep asking for an IRL use case for @tan_stack Start RSCs. Ok, here you go; partial page caching. CDN cache bust or TTL your pages at a component level granularity. I kept talking about it, but not showing it, so here is a deep dive video with code.

Want to learn about the new Solid 2.0 primitives? I got you! brenelz.com/posts/learning…

The fun part of having dramatically lower view counts after going on hiatus to work on TanStack AI is that I now get a flood of unsolicited emails from editors and thumbnail creators. It's always the same, a short one paragraph glazing me about the quality of my content, clearly written by AI, with some spiel about how they've already done the work and it's 100X better, I just need to pay them for it.

@rickyfm @ODrapeza @jantimon For those playing the home game: Qwik being the OSS version of Wix.

@rickyfm @ODrapeza @jantimon This article is about Wix? Am I missing something. And yes, we talked a lot about Qwik and Angular in the context of this feature.

Deferred Hydration is a huge for performance, and it's only (AFAIK) on TanStack.

I can't really speak for the team but it certainly isn't self-evident to me personally that Suspense was designed to be used for anything other than waiting for potentially long-running async work. Not for lazy hydration of components that are below the fold (as an example). And reading a lot of the other talk around this it's clear that a lot of folks attempted to "hack this together" using lazy loading and effects and what not, and either couldn't get it working completely to their satisfaction, or it was so complex to not be worth it. I get your point about the channel. That being said, we have a lot of experience with React and nobody was jumping in and saying "React already does that."

@jherr @MrFlashAccount @tan_stack How was it not evident that it was intended to work that way, when you used it exactly how it was intended to be used? And ya'll have a direct channel to the team, why didn't you ask?

This is a React feature btw, not framework specific. If you suspend during hydration React pauses hydration until you unsuspend. Tanstack is just wrapping the React feature in an API. <Hydrate> adds a suspense boundary, and suspends: use(props.gate.promise)

@rickyfm @MrFlashAccount @tan_stack Let's say that you are right. What does it say about the React API design that it wasn't evident to end consumers or framework authors that the feature was intended to be used for that purpose?

@MrFlashAccount @tan_stack Yeah I see what you mean, but this is different. This is intentionally designed to work this way and intentionally not abstracted to an API.

The new @code release adds Mermaid diagram rendering directly in the Markdown preview. The Integrated Browser also now supports HTML file previews and drag-to-select for pulling multiple page elements into chat context.

Astro starts static and asks "what should come alive?" Each answer is an isolated framework root dropped into HTML. Islands are independent runtimes sharing a DOM. Start is fully interactive out of the box and asks "what can wait?" The whole document hydrates as one React tree by default; boundaries are gates inside that tree. Context, state, and events flow through normally, hydration is parent-first, and React can break a gate early if correctness demands it. Same trigger vocabulary, different substrate: Astro composes isolated runtimes, Start schedules into one whole. That's why Start gets interaction(), condition(), and intent bubbling, and why Astro gets multi-framework.

@Nandan_k_chy I think that's gonna be my approach to demo'ing it. Here is a super hacky solution on top of lazy loading, that doesn't SSR, and blah blah. Here it is super cleanly.

@jherr Recently built my own solution for this. Allows hydration on visibility, or rendering client side only on visibility or immediately. Works on top of lazy loaded component. It was too hacky.

@moddi3io Yeah, when @schanuelmiller pitched I was like; "Ohhh... like Angular."

@GyenAbubakar No! Amazingly! @solid_js too!!!!

@jherr Only in React Start?

Most founders dream of VCs knocking on their door. @tannerlinsley has had that for years. And he keeps saying no! In my conversation with him, he shares the struggle of keeping @tan_stack, an OSS product used by millions of developers, free of monetary influence.

Agents are a lot more helpful when they can remember things. youtu.be/whyz0m302ZI Let me show you one possible way we'll be bringing memory support into @tan_stack AI.

Your AI stack just stopped being closed. 🔓 TanStack AI now speaks AG-UI client-to-server. - The same client hits any AG-UI server. - Any AG-UI client hits a TanStack server. Zero breaking changes. Migration guide in the tweet below 👇

After a very thorough 3 day full security sweep and hardening process, we'd like to issue an official all clear ✅ on TanStack repo and package security. Full details have been updated in our post-mortem and security followup blog (linked below). TL;DR: - Only the Router/Start repo was affected. 42 monorepo packages, 2 versions per package. These were promptly deprecated within the hour and removed by NPM shortly after - All other repos and packages were unaffected and remain secure including: Query, DB, Store, AI, Table, Form, HotKeys, Virtual, Pacer, Config, Devtools, CLI, Intent, etc. - All available and published versions of every TanStack package are safe to download, including TanStack Router/Start. tanstack.com/blog/npm-suppl… tanstack.com/blog/incident-…

I am very impressed by @tan_stack’s response to this. Fast, responsible, transparent and thorough.

This is one of the most requested features in TanStack AI, structuredOutput streaming. Well, now it's here, and even better, that was the last remaining key piece to bring about a mindblowingly good new feature in after it! Stay tuned. 😎

"Build a site where my whole family can drop in their favorite recipes — photos, the story behind each one, and little comments on each other's. Cozy magazine layout, warm cream tones, hand-drawn dividers, and a puff of flour that drifts across the screen the first time someone adds a recipe."

Good read. No long-lived publish token existed for the attacker to steal. They had to make our CI steal its own. Sophisticated attack. We already had a serious two phase PR/release mode before this.