TailwindCSS: Spring Cleaning and Fresh Foundations
The TailwindCSS team tackled some housekeeping with Robin Malfait leading a cleanup effort that bumped Next.js dependencies and dropped ESLint from their playgrounds. This change removed over 2,500 lines while adding just 119, resulting in a leaner development environment with fewer dependencies to manage.
Duration: PT3M52S
Episode overview
This episode is a short developer briefing from TailwindCSS.
It explains recent repository work in plain language.
- Show: TailwindCSS
- Published: 2026-04-04T10:00:37Z
- Audio duration: PT3M52S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Hey there, fellow developers! Welcome back to another episode of the TailwindCSS podcast. I'm your host, and wow, do I have some satisfying cleanup news for you today - April 4th, 2026. You know that feeling when you finally organize your desk and suddenly everything just feels lighter? That's exactly what happened…
Let's dive right into the main story because it's a perfect example of how sometimes the best changes are the ones that remove complexity rather than add it.
Robin Malfait just merged a fantastic pull request that's all about simplification. The headline? They bumped Next.js and completely dropped ESLint from the project. Now, before you gasp and think "Wait, they're dropping linting entirely?" - let me tell you the story here, because it's actually really smart.
Here's what happened: The TailwindCSS team only had ESLint installed because it came bundled with Next.js when you run `next lint`. They weren't actively using it for their main codebase - it was just hanging around in the playgrounds where they test things out. You know how it is - sometimes tools just accumulate…
Robin took a step back and asked the important question: "Do we actually need this?" And the…
What…