tailwind-merge
open-props
tailwind-merge | open-props | |
---|---|---|
12 | 49 | |
4,037 | 4,417 | |
- | - | |
9.0 | 8.4 | |
5 days ago | 5 days ago | |
TypeScript | HTML | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
tailwind-merge
-
Tailwind CSS for frontend teams: From settings to rules
So the library I use is tailwind-merge, which is a class that eliminates conflicts between classes when using Tailwind. So I created the following utility function.
-
Styling React 2023 edition
clsx is a tiny utility for constructing className strings conditionally, I use it in conjunction with tailwind-merge which merges Tailwind CSS classes without style conflicts.
- Tailwind vs. Semantic CSS
-
How to merge Tailwind class in Elixir Phoenix
I searched for a solution, and I found tailwind-merge which is written in JavaScript. Basically it finds conflicted classes and resolve the conflict. For example:
-
TailwindCSS & Template Literals
I would suggest you to use CVA and tailwind-merge.
-
Merge Tailwind CSS classes without style conflicts
Hey everyone! I built an open source library called tailwind-merge which helps with resolving style conflicts in CSS class strings. β https://github.com/dcastil/tailwind-merge
-
Why can I not override class?
I used tailwind-merge and cva to build my UI component library Rewind-UI.
-
Is tailwind used in real world when working at companies?What do you use to style your website
I use Tailwind + Next.js on most of my projects. Usually I add the following to the mix: - RadixUI+ tailwindcss-radix or HeadlessUI although I like Radix more - classnames - https://tailwindcss.com/blog/automatic-class-sorting-with-prettier - tailwind-merge - CSS Modules
-
How can I override Vue's behavior for merging classes?
I'm using Tailwind CSS and I'd like to integrate a library called tailwind-merge into my Vue app. I'd like the plugin to replace Vue's class appending behavior so that all components in my app have their Tailwind utility classes merged to prevent style conflicts. It may not be everyone's preferred solution to such a problem, but I think it's a very valid use cases for this sort of thing.
open-props
-
Learn CSS Layout the Pedantic Way
There's still some boilerplate, but I'm a big fan of Open Props[0] because it takes a hybrid approach. CSS isn't necessarily reinventing the wheel, but allowing for easier / more powerful approaches to difficult layouts or things that would otherwise require JS. Bootstrap is fine but troubleshooting advanced layout issues involves a lot of inspecting elements to see what styles are actually being applied (at least in my experience, YMMV) so I'd personally always bet on CSS.
[0] https://open-props.style/
-
Why Tailwind Isn't for Me
I don't quite get the hate for having CSS in another file. Do you also put all your react stuff in one single file ? That same logic and argument can be applied against all modularization.
And really 20-50 tailwind classes in a single element is VERY hard to read and keep in mind. No - it does not make things clear or understandable. One tends to need to re-read and scan over from the beginning and eyes glaze over. Esp if some elements only vary with a few classes missing. I guess it works for people with very high attention to detail and high amount of working memory. I only find it personally frustrating.
Maybe tailwind css works for some bright people. I did try it for a couple of projects and only felt pain.
However, the "atomic css" philosophy behind tailwind is great. I find framewroks like https://open-props.style/ far better to use.
- Htmx and Web Components: A Perfect Match
-
Styling React 2023 edition
Open Props adds to the set by providing extra custom properties for things like easing functions or animations.
-
The Future of CSS: Easy Light-Dark Mode Color Switching with Light-Dark()
> If you wanted to actually solve theming, what you should work for is not a constrained helper function like light-dark(), but instead a shared token schema. Today nearly every company has their own token schema and different ways of naming things in the semantic token layer. If we had a shard language here, not only would it be trivial to add light/dark theming (just redefine a few variables that are already provided for you), code could be shared between sites and inherit the theming/branding.
Isn't that the idea behind https://open-props.style/ (and https://theme-ui.com/ in JS land)?
I think it's a great idea, but hampered by the lack of adoption incentives for the very people that need to adopt it for it to become successful (design system/component library authors). It introduces constraints, but the promised interoperability is not really beneficial to the people who need to work within those constraints.
-
Tailwind CSS and the death of web craftsmanship
I do think that the real value of Tailwind comes from the utility classes, rather than css-in-html paradigm. You could achieve the same, for example, with Pollen.css [0] or Open Props [1].
[0] https://github.com/heybokeh/pollen
[1] https://github.com/argyleink/open-props
-
What is the best styling strategy for a Svelte project?
If you choose to style with plain CSS you can add design tokens as CSS variables with Open Props: https://open-props.style.
-
Released tw-variables: 400 useful Tailwind utilities as ready-to-import CSS variables
Some time ago I discovered Open Props which provides a lot of design tokens as CSS variables and started using it in some of my projects.
-
[Showcase] Searching for Friendly-User for Scrum-Tool Miyagi
CSS: Open Props (https://open-props.style/)
-
What UI framework would you recommend?
https://open-props.style/ gives you design tokens as CSS variables. Itβs CSS only and not Svelte specific.
What are some alternatives?
tailwindcss-classnames - Functional typed classnames for TailwindCSS
carbon-components-svelte - Svelte implementation of the Carbon Design System
classnames - A simple javascript utility for conditionally joining classNames together
svelte-headlessui - Unofficial Svelte port of the Headless UI component library
Tailwind CSS - A utility-first CSS framework for rapid UI development.
pollen - The CSS variables build system
clsx - A tiny (239B) utility for constructing `className` strings conditionally.
tailwindcss-intellisense - Intelligent Tailwind CSS tooling for Visual Studio Code
modern-normalize - π Normalize browsers' default style
headwind - An opinionated Tailwind CSS class sorter built for Visual Studio Code
vanilla-extract - Zero-runtime Stylesheets-in-TypeScript