Tailwind plugins

[benmccann]

I'd suggest offering the following via a multi-select:

• @tailwindcss/typography
• @tailwindcss/forms
• @tailwindcss/aspect-ratio
• @tailwindcss/container-queries
• @iconify/tailwind

Icons cause in Svelte people lots of problems, so I think it's worth making people aware of the iconify plugin since it avoids all the issues that people otherwise run into.

[dominikg]

icons should really be their own category and i'm really wary of promoting tailwind for its icon support if unocss with preset icons has the nicer dx and is more "vite".

[benmccann]

I don't know how it would work to put icons in their own category since you would need to have Tailwind or unocss installed for that adder to work. That would create a lot of tricky UX issues

It's arguable if unocss has a nicer dx. I think it's faster, but has worse docs, tons of dependencies, and a smaller community. But in any case, I think we shouldn't make Tailwind support worse just because some people like unocss. We already have a Tailwind adder and should make it as nice as we can. If we have an unocss adder it could add plugins in the same fashion

[dominikg]

you can also put unplugin-icons there or iconifys own svelte integration. maybe even some of the good quality standalone icon libs. It would be cool if we knew which other adders were already run so a tailwind user could get "hey, you use tailwind, there's a plugin for that..." like experience.

[manuel3108]

Relates: svelte-add/svelte-add#550

[manuel3108]

According to npm stats forms would be the one that is used the most (apart from typography). That should probably be the next one we try to add.

[benmccann]

I think it's just an import and then specifying it in an array for each plugin. Assuming that's true, we could probably build it in a generic way and add them all in one go