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
I’m currently building an effects library that utilizes tailwind. I would like to make the inclusion of each component a feature flag to reduce the binary size. I would hope components not included as features would have their tailwind not included as well. I think this could be accomplished with a ‘build.rs’ that runs the tailwind generation at compile time, but with how the current tailwind generation works, this may not be the case.
All that said, how are the appropriate tailwind classes scanned in the .rs files and resolved?
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.
-
I’m currently building an effects library that utilizes tailwind. I would like to make the inclusion of each component a feature flag to reduce the binary size. I would hope components not included as features would have their tailwind not included as well. I think this could be accomplished with a ‘build.rs’ that runs the tailwind generation at compile time, but with how the current tailwind generation works, this may not be the case.
All that said, how are the appropriate tailwind classes scanned in the .rs files and resolved?
Beta Was this translation helpful? Give feedback.
All reactions