SX Tailwind: Roadmap

[michalsanger]

Ideas for @adeira/sx-tailwind

Use Tailwind plugins #1330

The current implementation takes the Tailwind CSS file, parse it and builds an object for internal usage. This puts a lot of effort into the parsing and can't support customization (theming, custom colors, screen sizes, etc.).

Tailwind itself generates the CSS file from a collection of plugins. Each plugin can load tailwind.config.js which is a way the final CSS can be customized.

SX Tailwind should use the same approach, import plugins, let them process the config and build whatever is needed out of it.

Drop sxt method

Only tailwind(utilityClasses: string): string will be supported to copy how Tailwind is used.

sxt(...names: $ReadOnlyArray<TailwindClassNames>): string can't support customised Tailwind.

See #1365

Better error message when invalid utility name is used

See #1288

Tailwind UI

https://tailwindui.com is build on top of Tailwind and it would be great if SX Tailwind supports it.