Robin Malfait

Yep I see, the order inside of your CSS is indeed very important. In v4 how it works is that we sort all the utilities (and components) based on the...

Hey! While this works, I would recommend to use 2 sibling rules instead of the array syntax. We allow the array syntax at "runtime" for backwards compatibility reasons, but the...

Hey! Can you describe the actual issue you are running into? This looks like some styles are incorrect but Headless UI is headless and doesn't ship with any styles, so...

Going to close this since we haven't heard back. If you are still running into this issue feel free to ping me and/or open a new issue with a minimal...

Hey! In `@headlessui/react` v1 the `Combobox` could be marked as `nullable` which allows you to clear the value which in turn uses `null` as the `onChange` value when you cleared...

Hey! Now that v4 is out, it's unlikely that we are going to add new features to v3. That said, I am also not sure what the best approach is...

Hey! This is happening because of a minifier used in Next.js. As a workaround, you could add this workaround to your `next.config.js` file: ```js const nextConfig = { webpack(config) {...

@Multiply not yet, I have to create a minimal reproduction and open an issue, but wanted to give you a workaround in the meantime.

That might fix it, but I also think that Next.js is bundling the dependency instead of relying on it as an actual dependency. They also use `cssnano-simple`: https://github.com/vercel/next.js/tree/canary/packages/next/src/bundles/cssnano-simple

Opened an upstream issue with a reproduction: - Issue: https://github.com/vercel/next.js/issues/79149 - Reproduction: https://github.com/RobinMalfait/nextjs-incorrect-css-minification