Uncatchable Errors when component is unmounted asynchronously

[oscarleonnogales]

We have identified a few errors that zoid throws that cannot be caught by the implementation code (render.catch() and close.catch()). If the container element is removed from the DOM or the user is navigating away from the page mid-render, we should avoid throwing errors.

Here are 3 examples:
https://github.com/krakenjs/zoid/blob/main/src/parent/parent.js#L857
https://github.com/krakenjs/zoid/blob/main/src/parent/parent.js#L826
https://github.com/krakenjs/zoid/blob/main/src/parent/parent.js#L1172

These 3 error flows eventually cause the promise to be rejected since the render was never completed, and an error to be displayed on the console: https://github.com/krakenjs/zoid/blob/main/src/parent/parent.js#L732

Would adding additional checks to prevent an error from being thrown be sufficient?

[mdentremont]

Looks like some of this may have been started and then abandoned here