Love this. Preact v11 also features a simplified inline style implementation - part of the reason for the compatibility break. Works great with CSS Hooks v4-next. Congrats to the Preact team on the upcoming v11!

We believe styling should be expressive, colocated, and predictable. Today, we take that mission a step further with a new look designed to be as modern as the code CSS Hooks enables you to write. Experience the evolution in the first reply. 👇

Are you a @QwikDev in need of a simple styling solution? We've got you covered with our latest framework integration. Visit our website to get started...quick. 🙃 css-hooks.com

We recently published v1.4 featuring a new "recommended" hooks API that offers a convenient way to configure pseudo-class and media query hooks - with more options to come! All hooks are now opt-in, further reducing the size of your style sheet. Ours went from ~3.5kB to ~0.6kB!

5/6 Here's how it will look to use your new `css` function.

4/6 If you follow along, this is how your `css-hooks.ts` file will change.

This is now possible as of v1.3.0. All you need to do is name the hook accordingly.

As of v1.2.0, it's now possible to create hooks with complex "and/or" logic. One interesting use case is creating an advanced dark mode that respects both application- and browser-level preferences.

Did you know that the #HTML `style` attribute was supposed to permit #CSS rulesets (think `:hover`, `:focus`, and so on), but the #web browser vendors were unable to support this? CSS Hooks helps you recover this extremely useful feature. Get started at css-hooks.com.