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
It would be useful if Tailwind could optionally minify generated utility class names in production builds.
For example:
.overflow-hidden { ... }
could be transformed into something like:
.a { ... }
and all corresponding references in HTML/JSX could be updated automatically:
<divclassName="overflow-hidden"/>
→
<divclassName="a"/>
This could significantly reduce the size of generated CSS and HTML/JS bundles, especially in large applications.
An optional production-only optimization such as:
minifyClassNames: true
could enable this behavior.
I understand this would require safely tracking and replacing class references across the build, but it could be a useful optimization for reducing production bundle size.
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.
Minify generated class names
It would be useful if Tailwind could optionally minify generated utility class names in production builds.
For example:
.overflow-hidden { ... }could be transformed into something like:
.a { ... }and all corresponding references in HTML/JSX could be updated automatically:
→
This could significantly reduce the size of generated CSS and HTML/JS bundles, especially in large applications.
An optional production-only optimization such as:
minifyClassNames: true
could enable this behavior.
I understand this would require safely tracking and replacing class references across the build, but it could be a useful optimization for reducing production bundle size.
All reactions