We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TailwindCSS
tailwindcss-classnames
Node.js
Types for tailwind utilities that configured properly and working in application are not generating. For example:
https://tailwindcss.com/docs/adding-new-utilities#using-a-plugin
// tailwind.config.js const plugin = require('tailwindcss/plugin') module.exports = { plugins: [ plugin(function({ addUtilities }) { const newUtilities = { '.filter-none': { filter: 'none', }, '.filter-grayscale': { filter: 'grayscale(100%)', }, } addUtilities(newUtilities, ['responsive', 'hover']) }) ] }
Types for tailwind plugin utilities generated.
Use upper config file and try to generate types using CLI.
Ticket created as Issue, not as Feature because there is no information on main page that plugin utilities are not supporting
The text was updated successfully, but these errors were encountered:
This project only supports the official TailwindCSS plugins, namely, typography and custom forms plugins. However you could use https://github.com/esamattis/postcss-ts-classnames which supports postcss plugins
Sorry, something went wrong.
Also PRs are welcome if anyone wants to work on this feature
No branches or pull requests
Environment:
TailwindCSS
version: 2.1.0tailwindcss-classnames
version: 2.1.0Node.js
version: 14.16.0Current Behavior
Types for tailwind utilities that configured properly and working in application are not generating. For example:
https://tailwindcss.com/docs/adding-new-utilities#using-a-plugin
Expected Behavior
Types for tailwind plugin utilities generated.
How to Reproduce
Use upper config file and try to generate types using CLI.
Additional
Ticket created as Issue, not as Feature because there is no information on main page that plugin utilities are not supporting
The text was updated successfully, but these errors were encountered: