Next.js flags a critical patch for 26 August: get ready now
Vercel did something rare and right: it gave advance notice that a patch for a critical Next.js vulnerability lands on 26 August, in versions 16.3.3 and 15.5.24. The details come that day. What to do in the days before so you do not eat the exploitation window.
Tailwind CSS v4 in production: is the new engine worth the migration?
The Oxide engine, CSS-first config, faster builds. We migrated three real projects. What we gained and where it hurt.
INP one year on: how we keep interaction under 200ms
Interaction to Next Paint replaced FID as the responsiveness metric. A year later we know what actually moves the needle and what is theater.
Next.js 16 and React 19 six months in: what we actually used
Server Actions taking center stage, partial prerendering finally stable, and a build pipeline making less noise. Verdict in May 2026.
Web performance in 2026: INP has grown, LCP has not
Early 2026 Chrome UX Report data is clear: INP is the metric separating fast sites from slow ones. What it takes to stay under 200ms.
Web Components: rebirth or slow death?
Lit, Shoelace, micro-frontends. Are Web Components a serious choice in 2026? Our experience on three cases.
TanStack Start: the new Next.js alternative, is it worth it?
Type-safe routing, server functions, full SSR. TanStack Start tries to do to Next.js what Next.js did to Create React App.
Tailwind CSS v4: Oxide engine, CSS-first and no more JavaScript config
On January 22 Tailwind v4 went stable. Faster builds, CSS configuration, native container queries. Here is why we are migrating our projects.
React 19 in production: first two months, three things we liked
Stable in December 2024, in production by January. useActionState, native form actions, useOptimistic: what really changes.
Next.js 15 and React 19: what changes (and what breaks) in real projects
Async Request APIs, less aggressive caching, React Compiler in beta. Next.js 15 is the most impactful release since 13. What to adopt and what to delay.
Astro 5 and the Content Layer: content becomes data
Astro 5 unifies content collections, external CMSes and APIs. For content-heavy sites, the missing leap.
Tailwind: how many megabytes of JavaScript do we really save?
Tailwind kills CSS-in-JS and a chunk of JS runtime with it. Let us quantify the saving on three real projects.
Astro 3.0 and View Transitions: SPA-feel without the SPA weight
Smooth navigations like a real app, but with a static site. Astro 3.0 makes a big step and rewires how we think content-heavy sites.
Next.js 13.4 and the stable App Router: what really changes
Vercel marked the App Router stable in 13.4. Between Server Components, nested layouts and new routing conventions, here is what to adopt now and what to let mature.
