Adam Wathan

This should help: https://github.com/tailwindlabs/tailwindcss/discussions/7362#discussioncomment-2132610

Will have to dig in to this one to really understand the expected behavior because I think there's a chance this really is a circular dependency, but I have to...

Going to close this as a "won't fix" — to me it just doesn't make sense to be trying to add a `dark` modifier to a class that is already...

I think the double underscore idea is a good one. This will be a breaking change unfortunately but when we resolve it we can put the new behavior behind a...

Quick follow-up, one thing @thecrypticace pointed out to me that is a problem with the double underscore solution is that a triple underscore would become ambiguous: ``` a___b => "a_...

One solution in JSX is to use `String.raw` when you need to escape an underscore in a class, for example: ```jsx ``` This works as expected, because JS won't process...

@nbrombal Added a quick note here: https://github.com/tailwindlabs/tailwindcss.com/commit/3ef481af5242ca86777d4a1e1ff5630a5bb8efdb Glad to hear the `String.raw` solution is sufficient, going to close this one then with that as the recommendation 👍

Hey thanks for this! My only hesitation on merging is around the API — I've always sort of dreamed of coming up with a way to make variants somehow composable...

> Would it actually conflict with the idea in this PR, or is the concern more that you'd end up with some redundancy (and the small performance hit that would...

What order do you think the variants should be registered in? The registration order determines which styles "win" when multiple are added, for example: ```html ``` What color do you...