Depends really. If I have larger projects, I will use TypeScript as your "first point of testing" then becomes static typing. It will stop you from making some easy mistakes that can happen. If I am doing a short project or just writing short scripts, I don't bother. It becomes too much overhead.
The reason I actually decided to start getting into Tailwind is that I was using Styled Components with Styled System inside my design system and the cost maintain the types for those libraries became a nightmare that just wasn't worth it. I am still using TypeScript for the design system, but I am no longer bothering to type the styles. It just impeded on my ability to create way too much :(
Depends really. If I have larger projects, I will use TypeScript as your "first point of testing" then becomes static typing. It will stop you from making some easy mistakes that can happen. If I am doing a short project or just writing short scripts, I don't bother. It becomes too much overhead.
The reason I actually decided to start getting into Tailwind is that I was using Styled Components with Styled System inside my design system and the cost maintain the types for those libraries became a nightmare that just wasn't worth it. I am still using TypeScript for the design system, but I am no longer bothering to type the styles. It just impeded on my ability to create way too much :(
thanks a lot man ! appreciate it