This roundup covers JavaScript Weekly #809, React Status #496, and Node Weekly #646. The main takeaways for our stack are a fresh round of framework security fixes, Node.js 27's new alpha release model, and several early signals about how we build and test JavaScript applications.
On the OTP project we are moving to a monorepo with several microfrontends. At least three apps talk to Firestore, and all of them had their own copies of the same hooks: subscribe to a document, subscribe to a query, wait for the current user. The obvious move is to pull those hooks into a shared @repo/react-firestore package.
The catch is typing. Each app owns its own Firestore schema: workspaces/{id}/projects, users/{id}/chats, and so on. The shared package must not know those paths. But if the hook just takes path: string, we lose the typo protection we had when each app typed its own hooks.
This post shows the pattern we used: the package declares an empty registry, each app fills it in through declaration merging, and the package's hooks derive their parameter types from whatever the app registered.
This roundup covers JavaScript Weekly #808, React Status #495, and Node Weekly #645. The biggest takeaways for our stack are a critical Node.js security fix, Node 26 moving to LTS, and a couple of React ecosystem developments worth evaluating carefully.
TanStack AI 1.0 landed on npm on October 22, 2026, and the announcement post followed a day later. When we covered the beta in June, the pitch was the "Switzerland of AI tooling": any provider, any UI framework, the open AG-UI protocol on the wire, and no hosted platform attached. That pitch has not changed. What changed is the commitment behind it. The core APIs are now stable, 76 packages moved to 1.0 together, every API that 0.x had deprecated is gone, and a new agent harness ships beside the core as an explicitly experimental 0.x package. This post covers what "stable" includes, what landed between the August release candidate and 1.0, what an upgrade from 0.x costs, how the harness works, and what all of it means for Aliz projects.
This week's roundup covers JavaScript Weekly #807 from October 20 and React Status #494 from October 23. Node Weekly was off this week; its latest issue is #644, published October 15. Security updates published since then make that issue especially timely.
This week's scan covers JavaScript Weekly #806, React Status #493, and Node Weekly #644. React Status was off this week, so its latest issue is from October 9; the other issues landed October 13 and 15. The practical themes: dependency security, Node releases, and a few shifts in how teams choose their runtime and UI platform.
This week's scan covers JavaScript Weekly #805, React Status #493, and Node Weekly #643, published October 6–9. The standout themes for our stack: a new JavaScript toolchain, React ecosystem releases, and Node.js runtime updates.
An order has two units at $25 each. The browser editor shows $50. So do its downloadable invoice, confirmation email, and the terminal tool used by operations. Then someone changes the quantity to three. Every new representation should say $75—but updating a screen, producing a PDF, and sending another email are very different jobs.
React can participate in all four. That sounds like “write once, render anywhere,” until you ask what actually receives the component tree. A browser node? A document record? A string of HTML? A terminal frame?
The interesting part is not that several libraries accept JSX. It is where React's responsibilities stop and each destination's begin. We'll follow this hypothetical order across four outputs, separating shared business meaning from layout, input, and delivery. These are four output contracts, not four equivalent renderer implementations: email takes a different architectural branch.
Published October 5, this roundup covers the latest available newsletter issues, dated September 24–29: Node Weekly #642, React Status #492, and JavaScript Weekly #804. Here are the stories most relevant to our React, JavaScript, Node.js, and Vite stack.
This week's scan covers JavaScript Weekly #803, React Status #492, and Node Weekly #642, with a focus on what matters most for our stack: React, TypeScript/JavaScript, Node.js, Vite-era tooling, npm supply-chain security, and testing.