Javascript blog posts

Both of npm’s published email addresses are dead ends, and the support form needs a login you no longer have. Here is the escalation path that actually reached a human.

Frontier models score 48% to 51% on version-conditioned code generation. The documented cause is API churn, which stable platform APIs largely avoid.

Every gap React filled in 2013 now has a native answer, and three arrived in the last year. The evidence for choosing vanilla JavaScript in 2026.

Named contributors, open GitHub issues, and documented dependencies connect React’s team to shipped JavaScript features.

Built-in fetch, a native test runner, TypeScript without a build step, and a permission model: what Node.js absorbed into the runtime since 2013.

Import maps, Web Components, the Observer APIs, and View Transitions: everything the browser platform gained since React launched.

Every ECMAScript edition from ES2015 to ES2026, plus the browser APIs and Node.js built-ins that landed while the framework conversation moved on.

A bug report from a Laravel Blade project led here: Alpine.js and Livewire turn out to be sibling projects, sharing a creator and a real, named stack.

Alpine.js shows up across independent Shopify starter themes for a real reason. Here’s why it fits Online Store 2.0, with real production examples.

AI autocomplete doesn’t replace structural tooling for Alpine.js, it needs it. Real hallucination research, and why GitHub added LSP to Copilot itself.

From v1.0.0 to v1.5.0, Alpine.js Tools gained diagnostics, Go to Definition, and plugin support in VS Code, plus three bugs fixed along the way.

The migration that made Express the default for every Node stack I run: the bugs that started it, the research that held up, and four months of monitoring.