The Chrome team shipped Modern Web Guidance 1.0 on November 10, 2026, and a day later published the top 10 things AI gets wrong in web development. We first mentioned the project in our Google I/O recap when it was an early preview. With the stable release, it is worth a closer look.

This post covers what Modern Web Guidance (MWG) is, how it works, what it fixes, and how it fits our recommended tech stack. Short version: the guidance is good and mostly matches what we want. But two parts need care: our component libraries already handle some of the things MWG wants to rewrite, and the default install command breaks our supply-chain rules.

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.

"Rewrite it in X, agents are better at X" has become a common argument in frontend teams, and it almost never comes with numbers. Nolan Lawson's The AI cost of JavaScript frameworks (October 28, 2026) is one of the first attempts to measure it. He had the same coding agent build the same app in 12 frameworks, five times each, and tracked what it cost, how long it took, how much code it produced, and how fast the result loaded. This post summarizes the findings, the caveats that matter, and what they mean for the Aliz tech stack.

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.

This site was built with heavy AI assistance. That raises an uncomfortable question for the person who built it: if an AI can produce a frontend, what exactly is a frontend developer for? The internet has two loud answers, and both come with evidence. This post lays out the strongest version of each side, what they actually agree on, and what a frontend developer should be bringing to a team in 2026. It is written for engineers and for the people who decide whether to hire them.

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.

TypeScript 7.1 Beta landed on October 20, 2026. When TypeScript 7.0 shipped in July, the Go-based compiler was fast but had one big gap: there was no programmatic API. 7.1 closes it. It brings a new, stable-track compiler API, a plugin point called content mappers for non-TypeScript files like .vue components, and another big round of performance work. It also adds a few language and lib features. This post covers what changed, what it unblocks, and whether you should try the beta now.

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.