Support customisation by reading Tailwind config

[mariusmarais]

Currently group generation is static and shipped with the package.

Do that with the default Tailwind config, but also allow generating groups based on a project's tailconfig.config.js file so that customisation is possible. Things like TailwindUI then might just work automatically, or with minimal tweaks.

[Sheldonfrith]

Im using twcascade in a library I'm working on right now, so this issue is significant for me. I may be able to find some time to work on it, just wondering if you've started on a solution or have any advice regarding how you think this should be implemented?

[mariusmarais]

I have started to look at the Tailwind code, but have none of my own yet. I was hoping there would be a generic way to hook into Tailwind once, but that doesn't seem to be possible.

The standard TW modules are pretty consistent, but we would have to duplicate the generation logic here, AFAICS. Same for any plugins you want to support.

It would be a lot easier with direct assistance from TW, but certainly doable without.