Bug: Missing TPseudoClasses type when extends variants (tailwind.config.js)

Reproduce step: (v1.3.1)

• add custom variant in tailwind.config.js variants: { borderWidth: ['hover'], },
• generate new types: tailwindcss-classnames --config tailwind.config.js -o ./src/tailwindcss-classnames.ts

Expected:

All tailwind default TPseudoClasses with extended variants

Actually happening

Only get type for custom variants: export type TPseudoClasses = | 'hover:border' | 'hover:border-0' ...

P/S: Request feature: Generate type for custom plugin

plugins: [require('@tailwindcss/ui')]

[muhammadsammy]

Reproduce step: (v1.3.1)

• add custom variant in tailwind.config.js variants: { borderWidth: ['hover'], },
• generate new types: tailwindcss-classnames --config tailwind.config.js -o ./src/tailwindcss-classnames.ts

Expected:

All tailwind default TPseudoClasses with extended variants

Actually happening

Only get type for custom variants: export type TPseudoClasses = | 'hover:border' | 'hover:border-0' ...

Fixed in 423d5ba9ecfd7dc1e6121cd78745eaa222bd933c 👍

[muhammadsammy]

The “@tailwindcss/plugin” which I use here is just a plugin with custom classes and its not "https://tailwindui.com/. (Maybe it’s a part of tailwindui). https://www.npmjs.com/package/@tailwindcss/ui

I would like to add support for First party plugins. This is what I mean, we can have the types for tw 3rd-party plugin. https://github.com/aniftyco/awesome-tailwindcss#plugins

The postcss-ts-classnames project does exactly this. you will need to add the generated types from postcss-ts-classnames to the this package’s exported classnames function. Maybe will add a feature to the tailwindcss-classnames CLI that does this automatically.