Jordan Pittman

@carderne Yep, I can reproduce this in Linux — but not macOS. I think there's a difference in the order of events that still causes the bug to happen in...

@carderne I merged in another fix. It appears to work for me on Linux. Would you mind giving the insiders build a test? `npm install tailwindcss@insiders`

I updated the PR to use `list-style-type` for otherwise unknown types (the `any` type) which fixes the issue with `var(…)` _and_ the need for the additional `string` data type —...

We've prepped a feature for v3.2 (in #9396) that will allow you to do this! You can specify your content paths like so and we will look for them relative...

So, so, so much better! I still think the order of the before events should be reversed (out -> in) but I know why they're not in React at least....

This is also a problem for a non-cwd rooted path containing parens. If you attempt to escape them (with `\`) because the path is converted to unix style. Unfortunately, I'm...

@adamwathan I've updated the PR. So `preferOnConflict` is unnecessary here. That is only necessary when multiple sets of utilities can take the same arbitrary value "types" and share the same...

@belevy I'll take a look. Can you tell me what OS you're running on, the rough number of files that you're working with (`find . -name "*.html" | wc -l`),...

Hey, we've implemented a fix for this in React 17. There is a caveat related to Strict Mode however: There is a limitation of React itself before v18 and how...

In the next version of Headless UI we're exporting `XXXProps` types for each component. They are all generic because you can change which tag / component our components render with...