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
Tailwind is (and always has been) quite clear that you must include the full classname in your source to be picked up by the compiler. I always assumed this was a necessary but fully worthwhile tradeoff for what tailwind provides. But as often happens, it appears some people may have come up with a solution that get's us the best of both worlds.
I just came across Master Css, and it appears that one of their defining features is a hybrid architecture. As best as I could understand from a cursory read, css is precompiled, but they load a relatively small JIT compiler into the front end. This enables dynamic reassignment of css classes at runtime, but also dynamic assignments like text-{color}-600 on the backend, because any classnames not in your compiled css can have their css generated by the frontend JIT compiler.
I'm sure there are tradeoffs with this approach as well, but thought this was worth calling out for consideration. Tailwind has a great track record of keeping up with the competition by implementing their features when warranted, and I'd love to see that kept up!
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.
-
Tailwind is (and always has been) quite clear that you must include the full classname in your source to be picked up by the compiler. I always assumed this was a necessary but fully worthwhile tradeoff for what tailwind provides. But as often happens, it appears some people may have come up with a solution that get's us the best of both worlds.
I just came across Master Css, and it appears that one of their defining features is a hybrid architecture. As best as I could understand from a cursory read, css is precompiled, but they load a relatively small JIT compiler into the front end. This enables dynamic reassignment of css classes at runtime, but also dynamic assignments like
text-{color}-600
on the backend, because any classnames not in your compiled css can have their css generated by the frontend JIT compiler.I'm sure there are tradeoffs with this approach as well, but thought this was worth calling out for consideration. Tailwind has a great track record of keeping up with the competition by implementing their features when warranted, and I'd love to see that kept up!
Beta Was this translation helpful? Give feedback.
All reactions