Why We Ripped Twin out of 400+ Components

We replaced Twin with vanilla Tailwind in our monorepo, resulting in significant performance improvements, reduced dependencies, and better development experience (DX) for our team. We initially used Twin due to its ease of use and support for styled-components, but as our monorepo grew, we encountered issues with Babel's slow build times and compatibility problems with newer runtimes like SWC. After migrating to Tailwind, we saw pages load in under 1 second, compared to multiple seconds previously, and enjoyed benefits such as IDE extensions, the Tailwind playground, and easier debugging of styles. The migration required modifying over 400 components across 30 pull requests, but we were able to tackle it progressively, learning along the way and addressing precedence issues that arose during the process.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.