You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current CSS model using tailwind poses two issues:
When components are server side rendered, their html is made heavy by the amount of repeated classes there is. The weight of the page augments exponentially when adding new properties.
Overriding a property for one component (margin, size, white-space, ...) often requires the use of ! to bypass priorities. This does not leave room for later re-override when hacking.
We could solve both those issues by using classes placed in the @componentslayer of tailwind. The best automated way I could see to do that without changing our dev process would be to generate a tailwind plugin in each constants package along with the current bundle. This plugin would register the current classes as component classes like this:
Description
The current CSS model using tailwind poses two issues:
!
to bypass priorities. This does not leave room for later re-override when hacking.We could solve both those issues by using classes placed in the
@components
layer of tailwind. The best automated way I could see to do that without changing our dev process would be to generate a tailwind plugin in eachconstants
package along with the current bundle. This plugin would register the current classes as component classes like this:How do we do it?
...classes
using acorn...classes
using acornThe text was updated successfully, but these errors were encountered: