Alfredo Lopez

I ran across this recently in styled-system, and looked familiar. https://github.com/styled-system/styled-system/blob/6e00a16e0c53d865955c03df2d8d6ade8948bb2f/packages/core/src/index.js#L35 ` key = key && key.split ? key.split('.') : [key]` seems to do the trick. thoughts @developit ?

Hi @wallies @BenGamma @chrismclarke. Thanks for giving [Lightkeeper](https://github.com/lfre/lightkeeper) a try! I'd appreciate if you could give it a ⭐️ if you found it helpful. Thanks!

Hey @carlesnunez thank you so much for the inspiration and the kind words. I mentioned I created this https://github.com/lfre/lightkeeper-test/pull/1, in order to record a demo. Do you think the examples...

Hi @jbmoelker! Thanks for the issue, and for trying Lightkeeper! I think this is a fantastic idea. I really dig the consolidation. My main concern is that this table could...

The version bump is not enough. Next 13 expects a `renderToReadableStream` from react-dom, which is not currently supported in `preact-render-to-string`. This PR should hopefully unblock it: https://github.com/preactjs/preact-render-to-string/pull/259. That one is...

@demianrenzulli This is different than #43. The point here is that dynamic elements added to the same container would increase the `querySelectorAll` call unnecessarily. This can be avoided by allowing...

Hiya! If you really must, I patched Next with the least amount of changes to work with Preact again https://github.com/lfre/next-13-preact. Have fun.

For anyone coming across this. I've been supporting Next.13 with Preact and 14 by patching Next, and now Preact on this repo https://github.com/lfre/next-13-preact. Hope that helps!

Cool idea @yuvadm! Go ahead with it, and thanks for checking!

If you must, I patched Next 13 with the least amount of changes to work with Preact again https://github.com/lfre/next-13-preact. You can copy the `patches` folder and run `patch-package`