v4 third party plugins

[skttl]

Congratulations on getting v4 out!

I am missing documentation for creating third party plugins in the docs (v3: https://v3.tailwindcss.com/docs/plugins).

Is this not supported anymore?

[wongjn]

You should be able to do most things in a CSS file now, with new at-rules like @utility, @custom-variant, etc. For existing v3 plugins, you can include them via the @plugin at-rule.

[skttl]

Thanks

So, if I want to be able to share a plugin like on npm, it has to be in the v3 format?

[wongjn]

You can have it as a CSS file and consumers can @import it in their own CSS.

[skttl]

Thanks, the new at-rules looks great - need to play around with them :)

[browner12]

I see the container queries have been pulled in to the main codebase. What is the status of the other 3 (typography, forms, and aspect-ratio). Should those still be pulled in via the @plugin if you need them?

[browner12]

ahh, i see, thanks.

if you still need to target Safari v14 you probably still need the plugin to use the old padding bottom trick, rather than the native CSS properties.

[wongjn]

Do be aware that minimum browser compatibility for v4 for Safari is 16.4.

[stijns96]

@wongjn and what about forms and typography? I can imagine that these will remain plugins, but I'd like to rename prose to rte since Shopify is using the class rte on a lot of places. How can we do this now with @plugin?

[wongjn]

@plugin "@tailwindcss/typography" {
  className: 'rte'
};

[stijns96]

For those who use prettier, add /* prettier-ignore */ above it.