Tailwind v4 migration notes
What changed moving from config files to CSS-first tokens — and what we'd do differently.
We moved Makershot to Tailwind v4's CSS-first config. Notes from the migration.
What changed
tailwind.config.js→@theme inlineinglobals.css- Plugins configured differently in PostCSS
@import "tailwindcss"replaces@tailwinddirectives
What we'd do again
Define semantic tokens in :root and .dark before building components. Migrating colors after the fact is painful.
What surprised us
Custom utilities (ds-display, etc.) are easier in v4 — just add classes in CSS with @layer utilities.
Tooling
shadcn v4 works well with the new setup. Run their CLI against the CSS variable mode.
Related articles
Building a Real-time AI Summarization SaaS MVP with Next.js Server Actions, Streaming, and Vercel AI SDK
Launch your AI summarization SaaS MVP fast. Use Next.js 16 Server Actions, Vercel AI SDK, and backend streaming for efficient, developer-friendly builds.
Read articleDesigning Hyper-Efficient AI MVPs: A Tailwind v4 Guide for Next.js 16 & React 19 Indie Projects
Build lightning-fast AI MVPs with Next.js 16, React 19, and Tailwind v4. Learn practical design patterns and code snippets for indie founders.
Read article