tailwind-variants
                                
                                
                                
                                    tailwind-variants copied to clipboard
                            
                            
                            
                        🦄 Tailwindcss first-class variant API
As of tailwindcss v4 the theme config is advised to be done in a CSS file. I've upgraded a project that used responsive variants, which used `withTV()` to allow responsive...
### Description I use `tailwind-variants` to help write a top-level component library that will be used to implement a number of apps across my company. One requirement is that a...
**Describe the bug** Slot names can conflict with native function names. Native function is then stringified into class output. **To Reproduce** ``` const classNames = tv({ slots: { filter: 'flex',...
**Describe the bug** Using tailwind-variants with slots, compoundVariants, defaultVariants and explicitly passing the variants as `undefined` breaks. **To Reproduce** ```jsx import { tv } from "tailwind-variants"; const variants = tv({...
**Describe the bug** When extending a `variantInstance` multiple times using the `extend`, some variants properties (e.g., `tag`, `dot`) are lost. **To Reproduce** Steps to reproduce the behavior: 1. Create a...
**Describe the bug** When applying the className generated using the `tv` function, the color is not applied to the `::after` pseudo text. However, the color is applied when the text...
**Describe the bug** There is an error in the console saying the `__dirname` variable is not defined. The code that uses `__dirname` variable is included both in development and production...
In the [Tailwind Variants documentation](https://www.tailwind-variants.org/docs/getting-started), the example for responsive variants includes the xs breakpoint. However, xs is not a standard breakpoint in Tailwind CSS, as per the [official Tailwind CSS...
**Describe the bug** If combound variants exist, but no value in a variant, the types dont get inferred. It still works, but types are incorrect. **To Reproduce** [Reproduction Link](https://stackblitz.com/edit/vitejs-vite-u1sgmxf3?file=src%2Findex.tsx) **Expected...
**To Reproduce** Steps to reproduce the behavior: 1. While setting up tailwind-variants in next js 15.0.1 and using responsive variants it throws error as screenshot attached below. **Screenshots** ![2024-10-29 15...