zag
css-modules
Our great sponsors
zag | css-modules | |
---|---|---|
14 | 86 | |
3,654 | 17,368 | |
3.7% | 0.5% | |
9.8 | 5.5 | |
6 days ago | 19 days ago | |
TypeScript | ||
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.
zag
-
Top 5 Headless Components For Your React Application In 2023
Zag.js and Ark are headless component libraries created by the teams behind Chakra UI.
-
An Overview of 25+ UI Component Libraries in 2023
ChakraUI: An emphasis on A11y, meaning it is fully compatible with the WAI-ARIA accessibility standard, has won OSS awards, and has a thriving community. As mentioned, itβs one of the better choices out there as it has a great model for building composable UI, built-in hooks, and great dark-mode support. This is the same team behind Zag.js, which handles UI as state machines. Once again, youβd need to learn the API, and swapping might be hard to do.
-
What are your thoughts on wrapping all third party UI components with your own component to make it easy to replace libraries in the future?
I agree with what another poster said about Zag (also part of the Chakra project). It seems to me that eventually, with the explosion of number of frameworks, consolidation is going to happen. Segun is influential enough that Zag has a good chance of being what the consolidation ends up centering around.
-
Nuxt3 Best Tailwind Component Library
it's not perfect yet, but I find zagjs promising
- Zag.js β UI Components Powered by FSM
-
UI library that goes well with nuxt3.
Keep an eye on ZAG and ARK from the Chakra UI team, I feel like together with UnoCSS that could get very powerful.
-
Cool library that I recently discovered: Zag.js
π Head over to https://zagjs.com/ to learn more about Zag.js and get started with building accessible UI components in your web applications!
-
The one with styling Zag.js components with Tailwind CSS
The Zag.js documentation can be found here: https://zagjs.com/.
- Zag.js - UI components powered by Finite State Machines
- UI libraries with good keyboard support
css-modules
-
Selectors for Humans, Hashes for Machines
One aspect of CSS modules that I truly appreciate is its ability to compress class names into very short hashes. This feature allows me to keep my CSS selectors as long and descriptive as needed, while still compressing them into concise three or four character hashes. It aligns with my rule for CSS: selectors should be written for human readability, but compressed for machine efficiency.
-
Architecture: Micro frontends
Use methodologies such as BEM, and technologies including CSS modules, CSS-in-JS, and Shadow DOM to isolate the styles of each micro-application and prevent conflicts, thus ensuring reliable encapsulation and modularity.
-
Use TailwindCSS prefixes for shared design system components
For many years, Culture Amp took the second option, and distributed shared components without compiled CSS. This meant that every app that consumed shared components needed to include the necessary CSS build tooling β at that time CSS Modules and node-sass β with a compatible version and configuration. This was relatively easy to set up, but over time proved difficult to maintain. When node-sass was deprecated in favour of (the much faster but slightly incompatible) Dart Sass, this demanded a difficult lock-step migration across all those codebases, which we have yet to achieve. And as new applications have switched to Tailwind for their own styles, they've had to continue to maintain those old build tools in parallel for the shared components' styles.
- I'm Writing CSS in 2024
-
CSS Modules Still a Thing?
So CSS modules are a form of 3rd-party CSS-in-JS, where what you import are the class names, which are then usually obfuscated etc at compile time, and all the actual style declarations are (usually) compiled into a single css file or tag as part of the bundling process. You can read the og docs on'em here, and you've probably seen'em used in React like:
import styles from "./styles.css"; function Example(){ return (
Hello
); }They predate the ability to import non-js files in vanilla by a good while, and rely on the compile process to translate your
.css
files into.js
files that can be imported using whichever loader you use in your bundler.Import assertions are a vanilla way to import non-js files by telling the browser how to import them;
assert { type: "css" }
says to treat the file as CSS and create aCSSStyleSheet
,assert { type: "json" }
says to treat the file as JSON and create a JSON object - and hopefullyassert { type: "html" }
will hopefully arrive soon and create a#document-fragment
or something similar.Hope that clears it up!
-
An Overview of 25+ UI Component Libraries in 2023
Extensions of CSS: for example, Sass, Less, Tailwind, CSS Modules, to make stuff look a certain way on your own.
-
Creating a Component Library Fastπ(using Vite's library mode)
The components are styled with CSS modules. When building the library, these styles will get transformed to normal CSS style sheets. This means that the consuming application will not even be required to support CSS modules. (In the future I want to extend this tutorial to use vanilla-extract instead.)
-
All 7 ways to deal with CSS most never tried
NextJS comes with built-in support for CSS Modules which allows you to scope your styles locally in individual components without worrying about name collisions or messing up other parts of the codebase.
-
Vanilla+PostCSS as an Alternative to SCSS
CSS modules are not to be confused with mixins, as they serve the opposite purpose. While mixins are components or functions to be reused globally, modules are style sheets with a local scope used in a similar way as styled components in React.
-
The Future of CSS
CSS Modules CSS Modules is a pre-processing step: by default, styles are scoped locally to the current component, and the transpiler ensures no conflicts.
What are some alternatives?
primitives - Radix Primitives is an open-source UI component library for building high-quality, accessible design systems and web apps. Maintained by @workos.
emotion - π©βπ€ CSS-in-JS library designed for high performance style composition
themes - Radix Themes is an open-source component library optimized for fast development, easy maintenance, and accessibility. Maintained by @workos.
esbuild-plugin-solid
headlessui - Completely unstyled, fully accessible UI components, designed to integrate beautifully with Tailwind CSS.
stencil - A toolchain for building scalable, enterprise-ready component systems on top of TypeScript and Web Component standards. Stencil components can be distributed natively to React, Angular, Vue, and traditional web developers from a single, framework-agnostic codebase.
chakra-ui - β‘οΈ Simple, Modular & Accessible UI Components for your React Applications
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress π
linaria - Zero-runtime CSS in JS library
postcss-nested - PostCSS plugin to unwrap nested rules like how Sass does it.
a11y-twitter - Small changes to how you use Twitter to promote Tweeting in an accessible manner. For now, it will only prompt once per Tweet to add alt text to an attachment before you Tweet. Simple but effective. π
@artsy/fresnel - An SSR compatible approach to CSS media query based responsive layouts for React.