vanilla-extract
emotion
Our great sponsors
vanilla-extract | emotion | |
---|---|---|
90 | 52 | |
9,252 | 17,175 | |
1.2% | 0.6% | |
8.8 | 5.9 | |
13 days ago | 19 days ago | |
TypeScript | 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.
vanilla-extract
-
The best testing strategies for frontends
In our experience, the best testing strategy for modern frontends is a combination of E2E testing (using Playwright+NextJS), and unit testing. Visual regression testing is not worth the effort in our opinion, especially with the advent of better CSS tooling like TailwindCSS and Vanilla Extract.
-
Is there really anything better than Css Modules?
For building component libraries I’ve been a big fan of vanilla extract. Apparently it’s from the same people who made css modules
-
Introducing StyleX - the styling system used by Meta
This sounds exactly like Vanilla Extract. https://vanilla-extract.style/
-
An Overview of 25+ UI Component Libraries in 2023
KumaUI : Another relatively new contender, Kuma uses zero runtime CSS-in-JS to create headless UI components which allows a lot of flexibility. It was heavily inspired by other zero runtime CSS-in-JS solutions such as PandaCSS, Vanilla Extract, and Linaria, as well as by Styled System, ChakraUI, and Native Base. ### Vue
-
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.)
-
Tailwind CSS and the death of web craftsmanship
I do a lot of UI work and have never understood the appeal of Tailwind. It’s like relearning a new language. Tailwind was released in 2017. Maybe the CSS landscape wasn’t as good back then? Modern CSS is pretty awesome.
I’ve enjoyed using Vanilla Extract https://vanilla-extract.style/. It’s like css-in-js with none of the downsides as everything gets compiled to css.
-
PSA: Rust web frontend with Tailwind is easy!
Nah, I used enough Tailwind to know it becomes a spaghetti mess. I stick with CSS now, and in React I use https://vanilla-extract.style, compile time CSS in TypeScript.
-
What's the best option these days for CSS in JS?
Vanilla Extract is my current choice for the next greenfield project. I would also recommend checking out how and why this team integrated it with Tailwind.
-
Feeling lost on grokking large libraries
I'm not trying to call a particular org or library out, because I think the ones I've been digging through (and prompted me to write this) are very high quality. It's vanilla-extract (a build-time CSS-in-JS library) and Braid Design System (built on vanilla-extract).
-
Coming here from svelteland... is there a way to put CSS module inside JS?
Apart from what has been suggested, there is also https://vanilla-extract.style/.
emotion
-
Creating Nx Workspace with Eslint, Prettier and Husky Configuration
emotion [ https://emotion.sh ]
- Why is does modern HTML/CSS seem so complex and convoluted? (details in comment)
-
How are folks feeling about the React team's push toward server components?
dang, I never thought about this implication, and I googled the emotionjs repo there's a currently-active open issue regarding this https://github.com/emotion-js/emotion/issues/2928
-
I created a Zero-Runtime CSS-in-JS Library Compatible with Next.js App Router and RSC
Over my years of working with React, I’ve loved using CSS-in-JS libraries like Emotion and Styled-components. However, their inherent performance overhead from injecting CSS at runtime and their incompatibility with the latest Next.js features such as App Router and React Server Components (RSC) have always been a nagging issue for me.
-
Next.js App Directory Architecture First Impressions
An early difficulty I encountered was using UI component libraries like Mantine and Material UI in the new architecture. After looking through some GitHub issues, the culprit is Emotion, a package many component libraries rely on that does not support server rendering.
- How are you styling in NextJS?
-
CSS Style Guide for Web Dev?
In general I recommend using styled-components or emotion. These directly attach CSS to your components in a scoped way so that your CSS files aren’t stepping on each other’s toes all the time and make sure styling is colocated with the component.
-
Server Components
I ran into this problem as well. The root cause as I understand it is emotion: https://github.com/emotion-js/emotion/issues/2928
-
CSS In JS - The what, why and How's
While integrating component libraries, they may not give you full control over the order in which styles are inserted. (Example issue).
-
Lets create something neat together!
Vanilla Extract (CSS Framework) (Alternative: Emotion)
What are some alternatives?
stitches - [Not Actively Maintained] CSS-in-JS with near-zero runtime, SSR, multi-variant support, and a best-in-class developer experience.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
panda - 🐼 Universal, Type-Safe, CSS-in-JS Framework for Product Teams ⚡️
JSS - JSS is an authoring tool for CSS which uses JavaScript as a host language.
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
styled-jsx - Full CSS support for JSX without compromises
shadcn/ui - Beautifully designed components that you can copy and paste into your apps. Accessible. Customizable. Open Source.
linaria - Zero-runtime CSS in JS library
Sass - Sass makes CSS fun!