Why I Chose TypeScript Over Tailwind and Built My Own React Styling Library

My name is Maxim. I've been a full-stack software engineer for my entire career. And on June 4, 2022, I made an initial commit to a repo called react-box . I wasn't planning to build an open source library. I was deep in a project, writing React components day after day, and I kept noticing the same pattern: I'd build a component, then go create a CSS file for it. Or wrap it in styled-components . Or write a long chain of Tailwind classes. Every time, I felt like I was leaving TypeScript's world — the world where my editor knows everything, catches my mistakes, and guides me — to enter a world of strings where anything goes and nothing is checked. So I started extracting something. Not for GitHub stars. Not for a product launch. Just because I was tired of repeating myself. That extraction became @cronocode/react-box — a React component library where every CSS property is a typed prop. Why Not Tailwind? I want to be clear: Tailwind is a great tool. It solved a real problem for millions