twind VS compiled

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/

tags inside SFCs are typically injected as native </code> tags during development to support hot updates. <strong>For production they can be extracted and merged into a single CSS file.</strong></p> </blockquote> <p>There are also 3rd party CSS libs that do the same thing such as <a href="https://linaria.dev/">linaria</a>, <a href="https://vanilla-extract.style/">vanilla-extract</a>, and <a href="https://compiledcssinjs.com/">compiled CSS</a>. Which can be used in the event you're stuck with something that doesn't have baked in support via SFC formats (looking at you React).</p> <p>These are my preferred ways of handing it.</p> <ol> <li>Tailwind</li> </ol> <p>Option 2 is tailwind, which works backwards.</p> <p>That is, instead of the above with extraction where you write the styles, and the framework or libs extract them and replace them with class names, it's the other way around.</p> <p>You're writing class names first (which are essentially aggregated CSS property-values) which then generate and/or reference styles.</p> <p>It has the advantage of being easy to write (assuming you've got editor LSP, linting, etc), but as you've discovered, it's difficult to read / can get really messy really fast.</p> <p>As far as all the other claims on the Tailwind site, it's all marketing, at least 80% bullshit.</p> </div>

Your choice of CSS lib. Bootstrap can still be a valid choice, tho you may want to check the docs of whatever SSR / SSG framework you end up using as they may have better (or worse support). For example if you wanted to do CSS-in-JS (Next) i'd consider Linaria, vanilla-extract, or compiled.

So to be extremely clear, the issue isn't CSS-in-JS per se, it's just that the author only looked at implementations that don't generate create CSS files. He notably mentioned the (apparent) zero-runtime solutions Vanilla Extract and Linaria, only to skip them and complain that Compiled inserts nodes at runtime.

Compiled

Link: https://compiledcssinjs.com/

Compiled (Compile time CSS-in-JS solution from Atlassian)

Stitches Is near zero runtime and vanilla-extract claims it's zero runtime and typed. There's atlassian compiled as well but I never used it.

Author here, I haven't had time to play around with it, but this library[0] from Atlassian looks like a "best of the both worlds" styling approach: CSS-in-JS authorship without the runtime penalty.

[0] https://compiledcssinjs.com/