primitives
component-template
primitives | component-template | |
---|---|---|
26 | 7 | |
14,251 | 552 | |
2.7% | 0.5% | |
8.0 | 0.0 | |
6 days ago | almost 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
- 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
Hi HN! I'm Vlad, a designer and engineer on the Radix team (https://radix-ui.com). We just launched Radix Themes, an open source component library for building modern, accessible React apps.
Radix Themes is built on top of Radix Primitives (https://radix-ui.com/primitives), which companies like Vercel, CodeSandbox, and Supabase, among others, already use to power their interfaces.
Our goal is to help you focus on your product and build it faster instead of re-inventing common designs and working on the UI components over and over.
Under the hood, Radix Themes is built with TypeScript, React and vanilla CSS. All design tokens are CSS variables that you can tweak, overwrite, or use to build your own custom components with any styling solution that you like.
The idea to build Radix Themes emerged while working on our own design system at WorkOS (https://workos.com), which is the company behind Radix. There was hundreds of design details and edge cases that we had to take care of, so it still didn't feel like a solved problem.
We also were obsessed with getting the developer experience right. For every component we asked ourselves—what is the right API? What are the right props and parts? What should, and more importantly, shouldn’t be a part of this component? What API would make the code easy to understand and maintain, and what would put you into a messy situation that could bite when you don’t expect it?
With this approach, we used our own, battle-tested components that serve our paying users to kickstart Radix Themes.
I hope that you find Radix Themes useful. Right now, there’s 45 components, hundreds of carefully crafted variants, a few simple and powerful primitives for layout, and an extensive token system.
I would love to hear your feedback on our work and learn about your experiences with building UIs.
- 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
-
useControlledProps: Make any React Component Controlled/Uncontrolled
This is really cool, Radix UI uses a similar hook internally for their components. I like your implementation though.
-
Is form handling always a pain in the ass in React?
Remix is a dream. Once combined with Radix Form Component it'll be freaking heaven. https://github.com/radix-ui/primitives/blob/form-rfc/rfcs/2023-radix-form-primitive.md
-
Please give feedback on my personal company website
Looks like radix-ui.com, but a bit more boring tbh
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 - Beautifully designed components that you can copy and paste into your apps. Accessible. Customizable. Open Source.
svelte-adders - Easily add integrations and other functionality to Svelte apps
zag - Finite state machines for building accessible design systems and UI components.
svelte-headlessui - Unofficial Svelte port of the Headless UI component library
headlessui - Completely unstyled, fully accessible UI components, designed to integrate beautifully with Tailwind CSS.
svelte-materialify - A Material UI Design Component library for Svelte heavily inspired by vuetify.
chakra-ui - ⚡️ Simple, Modular & Accessible UI Components for your React Applications
svelte-material-ui - Svelte Material UI Components
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
shoelace-css - A collection of professionally designed, every day UI components built on Web standards. SHOELACE IS BECOMING WEB AWESOME. WE ARE LIVE ON KICKSTARTER! 👇👇👇
jest-dom - :owl: Custom jest matchers to test the state of the DOM