svelte-headlessui
polka
Our great sponsors
svelte-headlessui | polka | |
---|---|---|
22 | 7 | |
1,744 | 5,338 | |
- | - | |
6.6 | 4.4 | |
18 days ago | about 1 month ago | |
Svelte | JavaScript | |
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
- 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.
- What frustrates you in using Svelte?
-
Which UI components framework to use with Svelte project
Just in case you haven't seen it, I ported Headless UI to Svelte recently: https://github.com/rgossiaux/svelte-headlessui
-
Free alternative to Tailwind UI
About two weeks into my first project I did purchase Tailwind UI. It is a massively useful resource, and I use it several times a week. It is a great reference tool, and is being actively added to. I have definitely recovered my initial investment in time saved. If you're using React or Vue, it is a no brainer - support if first class (along with Headless UI). I actually pivoted to SvelteKit, and started using the Tailwind UI HTML components until recently when this dropped: https://github.com/rgossiaux/svelte-headlessui. I now start with the React component.
-
State of JS 2021 survey results are out
Sure, it's here. Unfortunately I'm still writing independent documentation--and as we know from the survey, documentation is the most important part of a library :)
polka
-
Serving static files with Node.JS
Express.js, with its long-lived version 4 is famous for its somewhat low performance. Other projects like fastify or polka have benchmarks outperforming Express.js. I don’t know why Express is slower, maybe because of regex processing of routes? If you’re using parametric routes like /users/:userid/entity and have no regexp routes, then replacing Express.js with fastify or polka will add a performance boost to your app. They are not direct replacements, but you can convert code if you really need that boost. In the article below benchmarks shows huge improvement, but in reality, your code will be a limiting factor to your app performance, and you are unlikely notice any improvement.
-
My Evaluation of SvelteKit for Full-Stack Web App Development
- once released and popular, they cease getting frequent updates
Now, yes this is a generalization. It doesn't apply to all of their packages, and not at the same point in time. But there is a pattern there. Some quick diving into the author's Github account, and their more popular repos shows the pattern. It's also clear that this was a choice made by a Svelte contributor to use their own package for "official" support in Svelte Kit.
When it comes to polka itself, I just don't get why a maturing framework like Svelte would choose something whose only real advantage lies in micro-benchmarking porn [1]. Speculation aside, I'm surprised the Svelte team didn't look at that choice through a lens of higher scrutiny. Koa would have been an infinitely better choice in my personal opinion, and there are several community-driven setups [2][3] for it.
[1] https://github.com/lukeed/polka#benchmarks
> sveltekit provides some kind of thin layer on top of express
It doesn't use express, but something named polka [1], which is much less mature. Bugs in polka have caused downtime and remote DOS vulnerabilities in my sveltekit app multiple times.
-
What are some packages that you used to solve problems that you encountered while developing applications?
Check out polka if you haven’t. It’s far leaner, and faster.
-
Looking For Light Weight Node API Framework
polka link
-
Deploying Sapper application to Deta.sh
Sapper, by default, uses polka as the server. I decided to use express instead.
What are some alternatives?
daisyui - 🌼 🌼 🌼 🌼 🌼 The most popular, free and open-source Tailwind CSS component library
SvelteKit - web development, streamlined
open-props - CSS custom properties to help accelerate adaptive and consistent design.
fastify - Fast and low overhead web framework, for Node.js
Preact - ⚛️ Fast 3kB React alternative with the same modern API. Components & Virtual DOM.
serve-static - Serve static files
tinyhttp - 🦄 0-legacy, tiny & fast web framework as a replacement of Express
fastify-static - Plugin for serving static files as fast as possible
Svelte - Cybernetically enhanced web apps
Express - Fast, unopinionated, minimalist web framework for node.
component-template - A base for building shareable Svelte components