tailwindcss-jit VS tailwindcss-rtl

I found this GitHub issue where someone wants to use CSS variables for padding, like so: p-[var(--app-padding)]

Just cruised the JIT docs & code on GitHub (merged into main branch).

> add non-default variations (mostly different heights/widths than what it ships with).

Check out https://github.com/tailwindlabs/tailwindcss-jit. It got released 3 weeks ago, and supports variable variables in width and height now.

About two weeks ago, Adam Wathan announced a new Tailwind experiment: Just-In-Time. In this article, I'll tell you what it's all about, and how you can take advantage of it.

In the latest Storybook update, we finally got support for PostCSS 8. So, to celebrate this occasion, I've put together a React Storybook environment that includes everyone's favourite utility-first CSS framework: TailwindCSS. The environment also utilizes the TailwindCSS JIT compiler & Webpack 5 to bring the build times as close to instant as possible. And to top it off, the repo includes a simple GitHub action that deploys the Storybook to GitHub pages every time something is pushed.

Tailwind CSS 2.0 with the Just-in-time version

It’s not a setup issue. The JIT works differently: there’s no “purging”. And the issue I described is a known problem: https://github.com/tailwindlabs/tailwindcss-jit/issues/71

Sidestepping the broader conversation, this "JIT tool" is apparently a postcss plugin, which means you have to spawn postcss process (e.g. at every save events or have build tool do the same).

Enter @tailwindcss/jit, a drop-in replacement (though not with 100% feature parity yet) that collects the classes used by your files and only generates the requested classes.

The latter was replaced by tailwindcss-rtl, which is instead a Tailwind plugin. It works great and requires very little effort, you just need to search and replace some non-RTL classes with RTL equivalents - which I expect to be easily swappable once Tailwind supports CSS Logical Properties.