vanilla-extract VS flynt

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.

For building component libraries I’ve been a big fan of vanilla extract. Apparently it’s from the same people who made css modules

This sounds exactly like Vanilla Extract. https://vanilla-extract.style/

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

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.)

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.

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.

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.

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).

Apart from what has been suggested, there is also https://vanilla-extract.style/.

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.

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.

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