svelte-headlessui
open-props
svelte-headlessui | open-props | |
---|---|---|
24 | 53 | |
1,790 | 4,767 | |
- | - | |
6.0 | 7.6 | |
8 months ago | about 1 month ago | |
Svelte | 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.
svelte-headlessui
-
10 game-changing tools that level up Svelte developers in 2025 💪
Svelte Headless UI is a library of unstyled, accessible UI components, inspired by Tailwind's Headless UI. It gives you all the interactivity without enforcing styles, allowing you to design the components exactly the way you want. With Svelte’s reactivity and this library's flexibility, building complex UI interactions has never been easier. Github repository →
-
10+ UI Libraries for Svelte to Try in 2024
GitHub: 1.8k stars License: MIT
- Ask HN: If you were to build a web app today what tech stack would you choose?
-
We need more headless ui library, and I just spotted a good one
As a side note, my project was the first to be published under the name svelte-headlessui and is both more popular and more complete than the other project. I don't know why the other guy picked an identical name but it drives me a little nuts because of how unnecessarily confusing it is.
-
Svelte Ecosystem in 2023
There is an unofficial Svelte port here but it doesn’t appear to be maintained so there may be a better option… that said there are a ton of better options if you want to use Tailwind with Svelte.
-
Passing event handlers in $$restProps? (ex. creating a wrapped <Input /> component)
This and passing styles to slots, are biggest bottlenecks in wrapping components (your use case) and creating headless components (see headless ui).
-
Svelte doesn't have an ecosystem as rich as React is ridiculous
Headless UI as in svelte-headlessui?
-
What Svelte UI Library Should You Use?
Svelte Headless UI should get some new PRs merged soon based on some comments u/ryangossiaux posted in the repo less than a week ago. He stepped away from the project for a bit after putting in a tremendous amount of work into it, and as someone who has used his library alongside Tailwinds UI on a number of projects, I’m super thankful for what he’s managed to do, and I hope that more people from the community will help support the project.
-
SvelteUI v0.7.0 is out - 14 new components and composables, new Dates and Preprocessors packages and more!
The component's come pre-styled. Styles can be overridden by tailwind classes, and here's a guide for that on the docs! If you want to use components that don't come pre-styled, I would suggest using something like Svelte Headless UI.
- What frustrates you in using Svelte?
open-props
-
How to Add an Excel-like Table to Your Astro Site (the Easy Way)
ZingGrid is built with modern native web components for performance and resiliency, but as a side effect of that a lot of the components exist inside Shadow DOMs. Still wanting to allow users to style any part they desire, hundreds of CSS Variables were created to pierce these shadows. Below we show how they can be used in conjunction Open Props for added flexibility.
- Open Props – Supercharged CSS Variables
-
What is a component library and should you build your own?
Dozens of other tools, like Open Props, fit somewhere in between.
-
Eurovision Gradients
Now, for the red/blue-version, I took one of the nice linear() timing-functions from Adam Argyle's 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 are some alternatives?
daisyui - 🌼 🌼 🌼 🌼 🌼 The most popular, free and open-source Tailwind CSS component library
carbon-components-svelte - Svelte implementation of the Carbon Design System
Preact - ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.
pollen - The CSS variables build system
Svelte - web development for the rest of us
modern-normalize - 🐒 Normalize browsers' default style
component-template - A base for building shareable Svelte components
Tailwind CSS - A utility-first CSS framework for rapid UI development.
svelte-it-will-scale - Generate a chart showing svelte's overhead
unocss - The instant on-demand atomic CSS engine.
mantine-datatable - The table component for your Mantine data-rich applications, supporting asynchronous data loading, column sorting, custom cell data rendering, context menus, nesting, Gmail-style batch row selection, dark theme, and more.
dropin-minimal-css - Drop-in switcher for previewing minimal CSS frameworks