While building our design system on top of tailwind we also faced similar issues and the most annoying issue is the specificity issue.
Now it's not the issue with tailwind per say but using atomic CSS for any component library will be a headache, and you have to juggle with specificity knives.
Here's a summary tweet of problems we faced with tailwind class specificity
Anurag Hazra ⚛
@anuraghazru
We stumble upon this issue while building renderlesskit with tailwind at @timelessco
I didn't have the issue with specificity since we wrote a bunch of logic that abstract this away from having similar utilities on the same property, but I see where this error may occur.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I absolutely agree with your points.
While building our design system on top of tailwind we also faced similar issues and the most annoying issue is the specificity issue.
Now it's not the issue with tailwind per say but using atomic CSS for any component library will be a headache, and you have to juggle with specificity knives.
Here's a summary tweet of problems we faced with tailwind class specificity
I didn't have the issue with specificity since we wrote a bunch of logic that abstract this away from having similar utilities on the same property, but I see where this error may occur.