Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Extend Variants not working
See original GitHub issueVersion
"@nuxtjs/tailwindcss": "^3.1.0",
"nuxt": "^2.14.6"
This is my tailwind.config.js file
module.exports = {
variants: {
extend: {
display: ['hover', 'focus'],
},
},
}
I add variants but i can not see hover:block or hover:hidden in my classes. hover:block not working.
My tailwind.config.js file works because i use corePlugins, it works
corePlugins: {
// ...
display: false,
}
Issue Analytics
- State:
- Created 3 years ago
- Comments:7
Top Results From Across the Web
Extended variants not working in Tailwind 2.0.2 and Laravel 8
2 in a Laravel 8.44.0 project. I am simply just trying to add some styling to my active menu tabs. Here are my...
Read more >Extended variants not working in Tailwind 2.0.2 ... - Laracasts
Hi there,. I am using Tailwind CSS version 2.0.2 in a Laravel 8.44.0 project. I am simply just trying to add some styling...
Read more >Adding new component variants does not work as ... - GitHub
Some component is not possible to extend the variant because the variant is bound to the component's logic. The Button variant can be ......
Read more >Configuring Variants - Tailwind CSS
Because the order of variants is important, any variants added under the extend key are automatically ordered for you using a sensible default...
Read more >Create and use variants - Figma Help Center
To fix this issue, you'll need to rename the properties and values of the variant.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As it happens… It turns out that TailwindCSS 1.9.5 is brought in via @nuxtjs/tailwindcss
I resolved my problem by reading the docs for V1 of TailwindCSS (no extend in variants… just explicit preferences):
https://v1.tailwindcss.com/docs/pseudo-class-variants#disabled
Could you confirm this bug is fixed when upgrading to Tailwind 2?