As a tech lead (or whoever makes the technical decision), it looks very tempting to adopt the open source UI libraries, if possible. In the React.js land, I used a bit of Charkra UI and Reakit. Source: almost 2 years ago

I'm currently considering React-aria, HeadlessUI, Radix-ui and Reakit for reimplementing the user-interface for a customer, but I find it hard to choose. Source: about 2 years ago

I’ve got some libraries I’m looking into to fill the gap. Currently looking at radix, reakit, and react-spectrum. Source: about 2 years ago

Regardless of what you use for styling though, you should look into so-called headless ui components. These are hooks and components only focused on functionality and accessibility, which you then use to build your own styled components. Some examples are https://reakit.io/, https://www.downshift-js.com/ and https://headlessui.dev/. Source: almost 3 years ago

For common components, I can't recommend Reakit enough. It's a keyboard accessible, unstyled component library with dialogs, popovers, and much more. I use it for all of my personal projects nowadays. Combined with Framer Motion for animation and Styled Components for styling, it's a killer mix. - Source: dev.to / about 3 years ago

Attractions is a UI kit for Svelte that includes 49 components and a collection of helper functions. It uses Sass for styling. Although the Attractions kit seems promising and the components look really nice, it's not very actively supported right now and its future is uncertain. - Source: dev.to / about 2 months ago

We took our time evaluating different options and ultimately landed on a focused set of technologies: Next.js, TypeScript, Redux Toolkit, SASS, and Axios. This combination offers a powerful and manageable foundation for our project, avoiding the pitfalls of an overly complex tech stack. - Source: dev.to / about 1 month ago

Traditionally CSS lacked features such as variables, nesting, mixins, and functions. This was frustrating for Developers as it often led to CSS quickly becoming complex and cumbersome. In an attempt to make code easier and less repetitive CSS pre-processors were born. You would write CSS in the format the pre-processor understood and, at build time, you'd have some nice CSS. The most common pre-processors these... - Source: dev.to / 4 months ago

CSS stands for Cascading Style Sheets, and is a scripting language used to style web pages. SCSS stands for Syntactically Awesome Style Sheet, and is a superset of CSS. You can think of SCSS as the more advanced version of CSS, which comes with several features that CSS does not support, such as the SCSS nested syntax, as shown below. - Source: dev.to / 4 months ago

In the past, you’d need to rely on pre-processors such as SaSS or Less, but not anymore… Native CSS nesting has landed on all major modern browsers. - Source: dev.to / 6 months ago