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 purge feature is what makes Tailwind possible in many respects. The combined matrix of utility glasses that are generated produce extremely large CSS files and purging reduces that to only the classes you're using.
Rather than this subtractive approach, I propose an additive approach; Scan the source code but only merge classes that are found.
This would make it unnecessary to configure variants (like hover states on box shadows) because the scanner could simply detect the use of a variant and included the related classes in the merge.
This could potentially improve build speeds PostCSS webpack builds #2544
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
-
The purge feature is what makes Tailwind possible in many respects. The combined matrix of utility glasses that are generated produce extremely large CSS files and purging reduces that to only the classes you're using.
Rather than this subtractive approach, I propose an additive approach; Scan the source code but only merge classes that are found.
This would make it unnecessary to configure variants (like hover states on box shadows) because the scanner could simply detect the use of a variant and included the related classes in the merge.
This could potentially improve build speeds PostCSS webpack builds #2544
Beta Was this translation helpful? Give feedback.
All reactions