primitives
component-template
primitives | component-template | |
---|---|---|
29 | 7 | |
16,385 | 560 | |
1.5% | 0.5% | |
9.3 | 0.0 | |
8 days ago | over 2 years ago | |
TypeScript | JavaScript | |
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.
primitives
- Explaining Scoped Context in React with example
-
Hacky Way to Customize Shadcn’s Tooltip Arrows
While this approach works, I’m sure there are UI libraries that allow for easier and more flexible tooltip styling. However, it feels rewarding to have found a workaround for this. If you're interested in exploring other options, you might want to check out this discussion.
-
Headless UI alternatives: Radix Primitives, React Aria, Ark UI
Radix Primitives is a library of unstyled React components built by the team behind Radix UI, a UI library with fully styled and customizable components. According to its website, the Node.js, Vercel, and Supabase teams all use Radix Primitives. The library has 14.8K stars on GitHub.
- Radix Primitives: an open-source UI component library
-
React: Build your own composable, headless components
Fast forward to a week ago, I cloned the Reach UI and Radix UI codebase and started exploring. Large codebases are always difficult to comprehend. With some digging around and reverse engineering, I was able to create the first component listed in the Reach UI docs, the Accordion.
- Show HN: Radix Themes – A beautiful, open-source React component library
- 5 React Libraries to Level Up your Projects in 2023
-
I'm building Radix Svelte, an unstyled UI component library with a focus on accessibility.
Other things that led me to choose this path were: Most libraries that are ports, official or not, use the original name (e.g. Svelte Material UI); Radix UI's license is fairly permissive (https://github.com/radix-ui/primitives/blob/main/LICENSE), which is why I also don't think it matters that it's a company behind it. Same as why I don't see an issue with the name Preact, for example.
-
I made a tool for converting between different media formats (without uploading to a server)
For a react project I recommend https://radix-ui.com, it's got pretty good defaults
-
List of free Tailwind UI component resources
radix-ui.com
component-template
-
Should you compile components before publishing them?
Reason I'm asking is that the official component template has a build step that compiles it to pure js. But I just tried publishing it with no build step (so literally just button.svelte, index.mjs and package.json and it seems to work fine.
- Anyone have complete documentation on creating an npm package with SvelteKit?
- how do use Svelte templates with Yarn?
-
Build your own component library with Svelte
But what would it be like to build your own Svelte component library? Fortunately, there are several templates that you could start with, like the official template provided by Svelte and Svelte 3 Component Template, which are considered the go-to for building your own component library.
-
Design systems with Storybook - seeking suggestions
My question is: is there a good up-to-date Tailwind, Svelte, Storybook template out there? The one on Github is pretty old and was abandoned 5+ months ago. With the pace of change, I'm worried I'd bump into legacy bugs. I'm confused as to where to start because Svelte has an official component-template but its 10 months old. Also, which bundler is the best for a newbie? Lastly, should I use svelte-add or is there a more stable solution out there with support for Storybook?
- How to make a svelte library / a custom svelte component npm module?
-
What's the state of the art of authoring component libraries with Typescript?
The official component template still has an open issue pertaining typescript support, and there's several templates linked there. Given that time is a rare resource, and given that I frankly don't trust myself to make the right decision here up-front, I'd be interested in your thoughts and experiences. Are there trade-offs in the available TS templates? Or does one of them basically tick all the boxes already? If so, why is there no endorsed official TS template?
What are some alternatives?
shadcn/ui - A set of beautifully-designed, accessible, and customizable components to help you build your component library. Open Source.
svelte-headlessui - Unofficial Svelte port of the Headless UI component library
dub - Open-source link attribution platform. Loved by modern marketing teams like Twilio, Perplexity, Vercel, and Huberman Labs.
svelte-adders - Easily add integrations and other functionality to Svelte(kit) apps
zag - Finite state machines for building accessible design systems and UI components. Works with modern frameworks, and even just Vanilla JS
sveltekit-package-template - A barebones project that provides the essentials for writing highly-optimized, reusable packages in Svelte.
svelte-component-template - A highly-opinionated base for building shareable Svelte 3 components
react-spectrum - A collection of libraries and tools that help you build adaptive, accessible, and robust user experiences.
svelte-materialify - A Material UI Design Component library for Svelte heavily inspired by vuetify.
chakra-ui - Chakra UI is a component system for building products with speed ⚡️
sveltio