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
Use whatever you'd like, but there's a few advantages with this approach over Tailwind, Twind, UnoCSS:
49
49
50
-
* No [repeat styles](https://tailwindcss.com/docs/reusing-styles) on child elements (..no [@apply](https://tailwindcss.com/docs/reusing-styles#extracting-classes-with-apply), no `[&>thing]` on each style).
51
-
* No endless visual noise on every `<div>`. Use a local `<style>` per group.
52
-
* No difference in syntax between local and global styles. Universal CSS.
50
+
* No [repeated styles](https://tailwindcss.com/docs/reusing-styles) on child elements (..no [@apply](https://tailwindcss.com/docs/reusing-styles#extracting-classes-with-apply), no `[&>thing]` on each style).
51
+
* No repeated prefixes for media queries, hover, focus, etc.
52
+
* No visual noise on every `<div>`. Use a local `<style>` per group.
53
+
* Share syntax between local and external styles. It's just CSS.
53
54
* Regain your "inspect, play with styles, paste" workflow in your web browser!
54
55
* No suffering from lost syntax highlighting on properties and units.
55
56
* No high risk of eventually requiring a build step.
0 commit comments