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
So currently one can customize tailwindcss-forms by adding additional styles which override defaults, but that results in having both the defaults and the new style in the final CSS bundle. I think it would be really nice if tailwindcss could figure out which default styles are not in fact used and do not include them in the final bundle at all. So even if some class is used, but then part of the class is later changed, then that changed part should not be produced for the original class (unless it is somewhere else used unchanged). In the context of tailwindcss-forms, if I change border color to some other color, then there is no point in including also default border color.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
So currently one can customize tailwindcss-forms by adding additional styles which override defaults, but that results in having both the defaults and the new style in the final CSS bundle. I think it would be really nice if tailwindcss could figure out which default styles are not in fact used and do not include them in the final bundle at all. So even if some class is used, but then part of the class is later changed, then that changed part should not be produced for the original class (unless it is somewhere else used unchanged). In the context of tailwindcss-forms, if I change border color to some other color, then there is no point in including also default border color.
Beta Was this translation helpful? Give feedback.
All reactions