Thorsten Lünborg

Thanks! Will close then docs change has been deployed.

Yeah that's unfortunately a weid situation in the current ecosystem that I'm unsure how to resolve: Webpack prioritizes the `"browser"` field over the `"module"` field, for some weird historic reason....

Makes sense, but realistically I won't work on this for now. I hardly have time to maintain the lib and still need to come up with a Vue 3 version...

HI! Can you please provide a small reproduction, i.e. on codesandbox.io ?

Seems to be a bug indeed, and TBH I don't know how to approach it off the top of my head. Might take awhile.

I don't see this as a bug. Whenever the source `` sends new vnodes, the content changes. Wether or not that new content actually looks like the old content which...

The re-render of your components means that the portal receives updated slot content. The fact that this content is semantically the same doesn't matter - its new vnodes. That's how...

You are missing that the class that you define on the component will be added to its root element - which is the portal, not the div inside it. However,...

Oh, right, forgot about that limitation. I will add this to the caveats section in the docs later.

> or is that relationship lost during transport This. There's really no way to make this work.