Add Tailwind prefix to Flux generated classes

[jshah4517]

Flux version

v2.2.1

Livewire version

v3.6.3

Tailwind version

v4.1.11

Browser and Operating System

Chrome on MacOS

What is the problem?

We have a prefix on our Tailwind classes, is there a way to use that same prefix on the classes that Flux generates?

Code snippets

@import 'tailwindcss' prefix(sp);

How do you expect it to work?

Having a similar option on the flux import or having it automatically parse the tailwind prefix.

Please confirm (incomplete submissions will not be addressed)

• I have provided easy and step-by-step instructions to reproduce the bug.
• I have provided code samples as text and NOT images.
• I understand my bug report will be closed if I haven't met the criteria above.

[joshhanley]

@jshah4517 thanks for reporting! Flux doesn't currently support this, so I've converted this to a feature request.

[chrisdicarlo]

That's unfortunate - it's a dealbreaker for us as well: we also use a prefix.

[GC-Mark]

We were about to purchase Flux, but having found out it doesn't work with prefixes, we have had to look elsewhere for now :(

[joshhanley]

@chrisdicarlo and @GC-Mark sorry to hear that! At the moment I don't even know how we could implement prefixes. If you have an suggestions, we'd love to hear them!

[GC-Mark]

Yeah, i did take a quick look through the codebase to see how prefixing could be supported, but it does seem like quite a hard problem to solve, and i came up with no real viable solution unfortunately. I can see how the prefix could be fairly easily dynamically added to the components, but the problem arises from the Tailwind compile process being able to pick up these prefixed classes as they will be dynamically generated

[chrisdicarlo]

The only way I can think of would be to publish the flux assets and have a tailwind pre-compile step that prefixes all the classes. But I would need to dive deeper into the flux source to see if that's technically feasible.