vanilla-extract
flynt
Our great sponsors
vanilla-extract | flynt | |
---|---|---|
89 | 3 | |
9,252 | 681 | |
1.2% | 2.2% | |
8.8 | 9.6 | |
8 days ago | 2 days ago | |
TypeScript | PHP | |
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
-
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/.
-
What am I missing out about Tailwind?
To be fair, I don't like Tailwind either but styled-components is runtime CSS, Tailwind is compile time. You can achieve the same thing via CSS modules or vanilla-extract though.
flynt
-
Coming to Terms with Tailwind
The underlying problem I see that Tailwind solves is component-izing a single idea. It does that pretty well. You can point to a single stack of code and say "this one thing is a navbar" and it's easy to know where to make changes. No searching, no stress.
What I haven't seen Tailwind do well on my projects is respond to change in the same way other methods would. I'm not saying it isn't possible, just that the several projects I've seen, it was a big pain.
A method I've been quite fond of to accomplish the same task, but remove the difficulties this author's other posts articulate, is to recreate the concept of a component in a single folder. Much like you would a Vue single-file component. If you read the "Components" heading here you'll get a good feel for it by looking at the folder/file structure:
* https://github.com/flyntwp/flynt#components
That same idea I've enabled in a framework/language-agnostic way with an NPM module I created (not public). It watches the folder, namespaces everything like a single-file Vue component (using a manifest name or defaults to the folder name), and with a bit of config you can even do intelligent vendor/tree-shaking across all components and themes. You can even have components inherit theme sass/js files.
This solution is nice because devs get the "one source of editing" in a single folder, it's performant, and it's agnostic to language/frameworks. Point to a folder of components, specify a dist folder, and you're done unless you want to modify config. Parallel execution of all components being built, it's also fast!
I'm only saying all of this because I'm curious if there are Tailwind users out there that could teach me if Tailwind solves other problems I'm not seeing. Oor if this type of solution would be something I should open source. It ends up being a pretty simple Webpack file under the hood.
-
How does script.js work on Flynt WP components?
I've just started using Flynt WP for Wordpress custom themes and I really love it. However, I don't have much experience with how building js files (such as this for example https://github.com/flyntwp/flynt/blob/master/Components/NavigationBurger/script.js) work so I was wondering if anybody would be so kind to give me some quick advice on them.
-
How to add jQuery to the Flynt WP Starter Theme
I was wondering if it was possible to add pure jQuery to the Flynt WP Starter Theme, which is component-based. I'm not very comfortable using JS as they are writing it, but I just might have to learn it. I was wondering if there were other options. Here you can find their overall theme repository https://github.com/flyntwp/flynt and here an example of script.js https://github.com/flyntwp/flynt/blob/master/Components/NavigationBurger/script.js
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.
acf-builder - An Advanced Custom Field Configuration Builder
panda - 🐼 Universal, Type-Safe, CSS-in-JS Framework for Product Teams ⚡️
bricks - A modular WordPress starter theme powered by Bootstrap 5 and Gulp
Tailwind CSS - A utility-first CSS framework for rapid UI development.
bricks - Open-source natural language enrichments at your fingertips.
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress 💅
starter-theme - The "_s" for Timber: a dead-simple theme that you can build anything from
shadcn/ui - Beautifully designed components that you can copy and paste into your apps. Accessible. Customizable. Open Source.
theme - Tonik is a WordPress Starter Theme which aims to modernize, organize and enhance some aspects of WordPress theme development.
linaria - Zero-runtime CSS in JS library
minimum-viable-wordpress - A single-file WordPress theme.