stailwc VS twin.macro

The answer is that babel / webpack is very very slow. I have seen refresh times go down from 15 seconds to less than 1 when swapping out babel and twin.macro to swc + my custom tailwind transpiler stailwc.

I have also been working on stailwc https://github.com/arlyon/stailwc which is feature-complete enough to use in production, but is intended for use with css-in-js. The parser however is complete and should be fairly easy to reuse.

If you think this would be helpful, check it out here: https://github.com/arlyon/stailwc

If this is something you are interested in getting involved with, please have a look at the discussions here: https://github.com/arlyon/stailwc/discussions/2 or try it out on your own project. Please open issues if there are plugins you absolutely need, as I'd love to improve your build times by 1000%.

Over the last few days, I started a project in rust targeting swc to replace twin.macro, namely stailwc.

Twin Macro Github Repo. This is a great resource to help you pick up Twin’s syntax, learn more about the package, and keep up to date with the latest releases.

Personally I like twin.macro the most. It’s similar to the above but based on Tailwind.

twin.macro is a library that allows you to use these styles in your JavaScript code. This library works exactly like styled-components.

One of the more promising alternatives is twin.macro - a Babel macro that processes Tailwind classes to generate JS objects understandable by various CSS-in-JS libraries. The developer experience (DX) of using it is amazing as you not only get all of Tailwind’s features without much change to your code, but you also get much more flexibility - all that on top of the traditional benefits of CSS-in-JS. Here’s an example code:

twin.macro

If you use Tailwind with React a lot, and are wanting support for Styled Components, give Twin Macro a look. They're close to finishing support for TW v3 in their Releases section :)

The blocker for us using it is our use of an excellent library called twin.macro which is built against babel's transpilation APIs to parse tailwindcss directives at compile time so that they may be used with css-in-js libraries. This efficiently bundles your css so that you only ship the precise css you use. The problem is, it's all quite slow.