Feature request: tailwind @utility support

[kingmesal]

Is your feature request related to a problem?

I need to be able to apply font-awesome icons via embedded CSS for templated content (like a statically built site w/ 11ty.) Tailwind v4 needs classes like fa-solid and fa-chevron to be marked as @utility classes to be compiled.

I use tailwind and postcss in my processing pipeline, and thus, it is nearly impossible without changes to mix these together.

Feature description

In a very manual, search and replace style approach, I was able to modify all the classes in the all.css file, then it took about 15 minutes tweaking, but I successfully made a version of all.css that is tailwind v4 compatible.

The beauty of this is, only those classes being

all.txt

referenced are included in my final output. Huge WIN!

Is there any chance this would be one of the formats output as part of the packaging?

Alternatives

Manual, painfully manual....

Additional context

No response

Feature request checklist

• The title starts with "Feature request: " and is followed by the requested feature description
• This is a single feature
• I have searched for existing issues and to the best of my knowledge this is not a duplicate

[kingmesal]

I actually have an implementation of your latest release of FA. I use in my site I build with 11ty. Works great. It just would be nice to not have to do this myself. Even though I've gotten pretty fast at making the updates.

[brandonmcconnell]

This looks so good

[kingmesal]

This is my latest 7.0 version. For example, in my tailwind config css file (NOT JS)
I'm import the whole thing: @import "./font-awesome/pro.css";

Then in my postcss process anything that isn't being used disappears, so during development I have access to all icons and styles. Works great!

font-awesome.zip