Fix Portal children always being mounted

[marvinhagemeister]

This PR fixes an issue where the children of a Portal component would always be treated as new children, leading to incorrect componentDidMount calls. By switching to the raw preact render function we skip the dom from being destroyed in an update scenario.

The downside of this is that this definitely breaks the stacking scenario where multiple trees are rendered into the same dom node. I'm wondering if we should reject that case in general and push rethinking root handling after the X release.

Nevermind the stacking bit. Found a way to fix that too 🎉

Fixes #1780

[coveralls]

Coverage increased (+0.1%) to 99.688% when pulling 620509a on portals_destroyer into c4e2f37 on master.

[JoviDeCroock]

This is clever! Great job

[steffenmllr]

Awesome fix @marvinhagemeister - this is the bug I just ran into :) Do you plan on making a 10.0.0-rc.1 release before the X release ?

[marvinhagemeister]

@steffenmllr Good call, we should release another RC version soon. We need a bit more time on the docs site anyway. Th site is mostly ready and we're currently working on updating the content 🎉

[steffenmllr]

@marvinhagemeister sounds great! Is there an easy way to install from git master?
I've tried npm install preactjs/preact#master but this fails because of the monorepo since it does not find preact/compat (I think)

[JoviDeCroock]

if you npm install from a branch, then you will have to build. So you would have to include cd node_modules/preact && npm i && npm run build