twind VS Bit

I think TW syntax is great as a CSS shorthand. I think it can be a great tool for making highly descriptive styles in a far more succinct fashion. I think if you you use Twind compiler and you store TW syntax outside of your templates/JSX and you just compile it down to descriptive class names, that's a great use of Tailwind. Then you get the advantage of meaningful names applied to elements in the template, and if you need to refactor/fix a style, then you can find it much easier. It also makes it a lot more dynamic, which standard Tailwind which can be a PITA to make dynamic (e.g. for dynamic behavior in Twind, you can have functions that generate TW style strings and use interpolated strings without having to worry about if the build-time TW compiler understands all the possibilities).

But at least you like something. And I get why people like Tailwind, but I end up finding it constricting for behavior that results in dynamic styles. But I've tried Twind which is a runtime TW compiler and it fixes most of my complaints and it has the same SSR-ability like Stitches & Emotion.

The CSS-in-JS library solves problems of global nature of CSS and of specificity by providing scoping in a unique class-name. It has some cost attached to it i.e run-time which is being solved by order libs vanilla-extract-css. I'm a big fan of tailwind and I honestly believe it is enough for your project. If you also need dynamic styles then CSS-in-JS is better over tailwind, though there are solutions like twind which provide a flavor of tailwind with the CSS-in-JS approach they do have all cons of any CSS-in- JS libraries. I'm very excited about styles by Facebook and waiting for the day it will be open-sourced or CSS itself evolves to me provide scoping and be more modular, until that day comes I'm betting on CSS-in-JS with stitches and vanilla-extract-css.

what framwork are you coming from? i honestly wouldn’t try fresh unless you are using tailwind - bootstrap components are jsx based, and fresh is based off islands architecture which would make integrating the two trickier since youd have to route through deno + the preact compat lib. if you really want to do it, read into this. that being said, tailwind is a very powerful tool. i use it daily in nearly every element on front end, and as someone who likes avoiding design as much as possible ive found tailwind (and twind) are extremely pleasant to work with since it’s mostly class/keyword based styling as opposed to css / sass / scss styling

I want to do something similar with Remix to make a separate stylesheet per route with content coming from a CMS like WordPress. I’ve had my eye on Twind once they add compatibility with v3 and all the JIT stuff. https://twind.dev/

When initializing a new project, Fresh will also ask if you want to use Twind, which is a Tailwind-to-JS library. If you choose this option, then you will have the power of Tailwind without creating a config file or using PostCSS, which I thought is pretty cool.

Try https://twind.dev/

Using Bit and Bit Platform, components are shared and synced across separate repositories, allowing you to treat your poly-repo setup as one single virtual monorepo.

Before Bit became part of our workflow, sharing and collaborating on individual components felt like climbing a steep mountain. Managing dependencies, packaging, documentation, and setting up elaborate build tools wasn’t just time-consuming — it was frustrating. These setups often relied on third-party tools that were prone to issues, introducing bugs and bottlenecks along the way.

Bit Documentation

By leveraging tools like Bit and [Ripple CI], developers can unlock the full potential of build-time micro frontends, creating applications that are not only modular and maintainable but also efficient and cohesive. It’s time to give build-time integration the spotlight it deserves and embrace a future where distributed frontends are both powerful and user-friendly.

Bit. Composable software.

Some component collections like shadcn/ui offer a CLI tool to help you with the “copy-paste” process. Other tools like Bit can help you do the same with any UI library hosted on the Bit Platform. Any component can either be installed or copied into your project.

Bit has introduced a new entity to the world of web development: The Bit Component. In short, a Bit component can be thought of as a super-package. You can share it, install it, copy it, and even collaborate on it independently of any particular project setup.

Official Website

This actually has a lot of potential I think. It reminds me of https://bit.dev (obviously without most of the main features). But the core is there - the idea that components should be organized in a way that makes them easily reusable.

If you were to add a preview functionality of each component, this would already look A LOT like the Bit platform.

Personally, I've been trying to figure out a way to create a component library where my components are easily shareable and importable, but haven't yet come to a real solution. Bit is a good one but I am not yet ready to pay per component after my 20 free components are used up.

I think this would be actually extremely useful to me personally if you added these two things:

- component live preview (perhaps with mock props/data?)