Muhammad Sammy

Any updates on this?

That would save a tremendous amount of time. Thanks for the suggestion! :+1:

Done. :+1: Thanks a lot!

I noticed that the `peer` classname is also missing. Should the utility contain both?

I think you are right. I don't have a name for the helper and if we made one helper for both utilities, it won't be easy to for the user...

I'm updating the README until this is resolved. Thank you!

That would be very cool. Thanks!

I think this is because you are using an old config (v2) which is not compatible with v3 in which the closures evaluation has changed: v2: ```js module.exports = {...

Well thought. I think the generics approach looks better :+1: Sorry for the late response, I've been very busy.

This project _only_ supports the official TailwindCSS plugins, namely, [typography](https://github.com/tailwindlabs/tailwindcss-typography) and [custom forms](https://tailwindcss-custom-forms.netlify.app/) plugins. However you could use https://github.com/esamattis/postcss-ts-classnames which supports postcss plugins