GitHub's Three-Year CSS Migration Cuts Server Render Time 55%

A styling system rebuilt without a visible outage

GitHub's Primer design system team has spent roughly three years replacing the CSS-in-JS approach behind every button, banner and breadcrumb on GitHub.com with CSS Modules, a format that ships plain CSS instead of generating styles at runtime in the browser. The team, in an engineering blog post published this month, said the trigger was simple: as the number of components on individual pages grew starting in 2023, the existing runtime styling approach slowed initial page loads, degraded server-side rendering, and made every style update more expensive to ship. For an organization the size of GitHub, that meant a customer-facing performance problem showing up gradually across millions of page loads rather than in a single outage.

The bigger cost wasn't the components — it was every team using them

Migrating Primer's own components was finished by December 2024 using feature flags and visual regression tests to catch breakage before it reached users. The harder problem was a customization prop called "sx," which had become the default way for GitHub engineers across the company to override component styling with inline objects. Removing the underlying CSS-in-JS library required tracking down every one of those usages first — a scope of work that extended far outside the design system team itself and into GitHub's main product codebase.

AI coding agents compressed the final stretch

That six-month push ran from April to October 2025 and delivered server-side rendering gains of 1% to 22% on affected pages, with a rotation of eight engineers migrating 6,419 of the roughly 7,760 sx props identified at the outset. GitHub's account does not detail what happened over the following months beyond noting that Copilot's coding capabilities were improving in parallel. By the time the team returned to the remaining work in April 2026, 895 sx props were still outstanding. A much smaller crew of two engineers, using Copilot coding agents, cleared that backlog in about three weeks. By June 2026, GitHub reported running entirely on CSS Modules, having fully removed the styled-components and styled-system libraries from its production codebase — closing a migration that began before generative coding tools were part of the workflow and ended with them doing a meaningful share of the mechanical labor.

What it tells a budget-holder about re-platforming costs

This is one company's account of one migration, not a benchmark for how long or how much similar technical debt cleanup costs elsewhere — GitHub's engineering scale and in-house tooling (a custom VS Code plugin and codemods, on top of Copilot agents) are not universal. But the numbers GitHub disclosed give budget-holders a concrete reference point for two things that are often estimated loosely: labor curves and safety infrastructure. The bulk of the manual migration took eight engineers six months; the AI-assisted final phase took two engineers three weeks. Neither phase moved without feature flags, staged rollouts, and visual regression testing already in place — safeguards that are easy to leave out of a migration budget until something breaks.

Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: github.blog.