Luis Herranz

> Moreover, we can't use x-show in this case either (I believe), because it adds a display:none if it isn't open, so it interrupts opening the submenu on hover. So...

Yeah, I think we can consider this finished, at least for now. Let's focus on [replicating the Alpine directives with our own](https://github.com/WordPress/gutenberg/pull/44509) 🙂

If you give me some instructions, I can work on the PR.

Another take at [deep signals, based on Proxies](https://gist.github.com/luisherranz/ec16177c07efb6a50e89b50dda08f7e8). _[StackBlitz with examples](https://stackblitz.com/edit/vitejs-vite-kynewn?file=src%2Fmain.jsx,src%2Fdeep-signal.js)_ I'll refine it a bit (add tests, avoid wrapping unsupported elements and built-ins, etc) and publish an npm package...

Inline {} code may also contain mixed JS/XML syntax: ```jsx const Count = ({ count }) => { return ( {count > 10 ? : } ); } ```

I see. Thanks Josh.

I took a look at this problem and it is interesting because this is not an actual bug. At least not yet. This warning is caused because React, in `StrictMode`,...

In case you are curious, this is my proposal to add support for React Concurrent: https://github.com/RisingStack/react-easy-state/issues/228

Hey @EidenEidenEiden, thanks for the heads up 🙂 Frontity `connect()` doesn't support `forwardRef` components yet because the underlaying implementation (`view()` from `react-easy-state`) doesn't either. I opened an issue in the...

Interesting. > - Background URL on client: /static/images/image.jpg > - Background URL on the server: __webpack_public_path__images/image.jpg It is related to this PR, where we started populating the dynamic public path...