When Dropbox engineers noticed their backend monorepo had crossed 87 gigabytes, the first instinct was probably the same one you'd have: somebody committed...
Two months ago, Microsoft dropped the TypeScript 7.0 beta — a complete rewrite of the compiler in Go.
Every Core Web Vitals score you've ever seen for your single-page application is incomplete. Not wrong, exactly — just measuring the wrong thing.
For four years, Vite's dirty secret was that it ran two completely different bundlers depending on whether you were in dev or production.
Deno just posted a 34-point jump in Node.js test suite compatibility in a single minor release.
Endor Labs put GPT-5.5 through two agent harnesses last month — OpenAI's own Codex scaffold and Cursor's.
Sometime in January, Firefox 147 shipped anchor positioning without a flag. Safari 26 had it.
Every quarter, someone on the team floats the idea of migrating off Spark.
Every agent framework defaults to sequential tool calling. Ask a question, get a tool call, execute it, feed the result back, repeat.
In 2019, Chrome shipped loading="lazy" for images.
The language you use to make JavaScript safer just stopped being written in JavaScript. TypeScript 7.
Every streaming team has a state budget, and joins eat most of it.
Every Vite project that shipped in 2025 ran on two separate bundlers.
Every project I've touched in the last five years has a file somewhere — maybe lazyVideo.js, maybe useMediaObserver.
Every SvelteKit app I built before version 2.39 had the same awkward middle layer: a +server.
Last week I added a fifth MCP server to a coding agent I've been running in production. Response quality dropped off a cliff.
Vite 8 landed on March 12 with exactly one headline change: Rolldown replaced both esbuild and Rollup as the bundler. Two dependencies out, one Rust binary in.
The React Compiler hit v1.0 in October 2025.
TypeScript 7.0 beta dropped on April 21.