Next.js 16.3 Lands Instant Navigation, npm Worm Hits Keyv, and CSS Anchor Positioning Tops Dev Wishlists
The keyv/cacheable worm is an active supply-chain compromise still spreading through transitive dependencies — any project pulling those namespaces needs an immediate audit. Next.js 16.3's instant navigation and the CSS survey's anchor-positioning enthusiasm both point to a frontend that is getting faster and more expressive, but still gated by runtime compatibility.
Next.js 16.3 brings instant page navigation, faster builds, SSR performance upgrades, and optional TypeScript 7 type checking. The release also includes AI-related optimizations. Separately, Node.js 26.7.0 arrived two days after 26.6, adding a `--test-coverage-include-all` flag that pulls uncovered files into coverage reports and fixing crashes in FFI and SQLite modules.
A credential-stealing worm infected the popular npm packages keyv and cacheable, and the breach has since cascaded to hundreds of other packages. The 2026 State of CSS survey named anchor positioning the most-loved new feature, though poor browser support blocks production use; `:has()`, `aspect-ratio`, and CSS nesting lead actual adoption. AI tool usage among CSS developers remains low.
Two articles tackle data integrity: a Playwright-based soak test catches SPA memory leaks by looping user flows and monitoring DOM nodes and event listeners until CI fails, and a deep look at JSON serialization shows how `JSON.parse` + `JSON.stringify` silently corrupts large integers, undefined, and Date objects.
Anchor positioning topping the CSS wishlist while failing the compatibility threshold is a recurring frontend pattern: the features developers want most are often the ones browsers ship last.
The keyv/cacheable worm spreading to hundreds of packages shows how deeply a single compromised maintainer account can cut when popular namespaces act as transitive hubs.
JSON round-trip corruption is a well-known footgun, but the explicit framing of `JSON.parse` + `JSON.stringify` as a lossy transform — not a faithful serialization — is a mental model most codebases still lack.
Soak testing SPAs by counting DOM nodes and event listeners inside a CI loop is a cheap, high-signal regression guard that very few teams actually wire up.