I haven't used Tailwind a lot, but I pointed it at my clj/cljc/cljs sources, and it worked out of the box. What does this plugin do that the native compiler doesn't?

If that’s worked for you, no need to use this. We had to point it at the JS output, as it missed stuff otherwise.

But did you try pointing it at your Clojure sources?

Yes, it typically missed things with fractions such as 1.5 etc. to be honest, this was three or four years ago though, so it may well have improved. The other thing is that we write our classes as keywords (for autocompletion etc), which may have something to do with it.

That is interesting. At my work did it on the minified JS, since that will trim functions that do not get called (which is harder to do by looking at the clojure files).

The built-in scanner for tailwind did not work, because we have taken advantage of the hiccup syntax like :div.class-1.class-2

I don’t remember if I made provisions for the dot syntax. If not, I will add it.

@U08JKUHA9 the built-in scanner finds those now 😊

Ah nice, I'll need to revisit that code

It does not recognize keywords however, but other than that it just works

The hiccup dot syntax is explicitly a keyword though, isn’t it? Or can it be written as a string?

Last I used tailwind with cljs it was picking up keyword classes just fine

I may misremember then!

I am certain that it works with hiccup style tags with classes (keywords)

This is our app without and with custom extractors. I’ve spent so much time debugging why Tailwind sometimes works and sometimes doesn’t. YMMV of course, but none of it is universally supported with standard Tailwind extractors.