Jason Miller

Also interesting: the bug doesn't happen in CodeSandbox's browser preview, only when viewing the Preact version in a proper Chrome tab/window. I haven't been able to get to the bottom...

What is the reason for using both type definitions at the same time?

Echoing from various discussions elsewhere: the `j/2` child search optimization was never supposed to apply to keyed matches, which to me makes this a bug rather than just a performance...

Interesting - this is an unfortunate effect of an optimization Preact does: we "detect" small swap or shift movements within a list of keyed items and only invoke a single...

@mjgerace I believe Jovi has a PR Open in render-to-string to add the necessary links for this.

Possibly, yeah. Maybe the upgrade switched his build to use MJS and that caused the import to fail instead of returning `undefined`?

It looks like Next.js is repeatedly re-rendering the route (there are 5 calls to `preact.render()`), but I think this may be caused by Preact bubbling thrown errors past components with...

Can confirm - my PR fixes this, we'll just need to figure out whether the change is something Preact can land without breaking stuff (since it affects how Suspense works)....

@jaydenseric you can achieve this without the proxy by creating a fake DOM element to pass to Preact's render() or hydrate() methods: ```js // A fake DOM element we pass...

Also - as an added bonus, `PersistentFragment` works with ``: ```js import { createPortal } from 'preact/compat'; const fakeRoot = new PersistentFragment(document.head, children, end); // as above function App() {...