You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This error occurs when multiple x/y components are rendered then destroyed/unmounted for new components.
The error is caused by @unovis/ts attempting to render destroyed components in updateContainer. The error itself is Node.appendChild: Argument 1 is not an object. in the re-insertion loop within updateContainer:
// Re-insert elements to the DOMfor(constcofthis.components){this.element.appendChild(c.element)}
I believe this occurs due to svelte 5's deep reactivity once again. If you have more then one x/y component the first component is destroyed / unmounted and the component.destroyed function is called, this triggers the updateContainer typescript function with one component still remaining, while this is occuring the other component is destroyed but is still present in the config.components array, therefore this loop attempts to append an undefined object.
The fix for this as far as my testing is doing config.components = config.components?.filter((c) => !c.isDestroyed()); before calling updateContainer.
The other problem is the component lifecycle action's destroy function is called before the line.svelte onDestroy callback is called. Since the onDestroy callback is responsible for marking the component as destroyed the lifecycle action doesn't remove the destroyed component.
The text was updated successfully, but these errors were encountered:
This error occurs when multiple x/y components are rendered then destroyed/unmounted for new components.
The error is caused by
@unovis/ts
attempting to render destroyed components inupdateContainer
. The error itself isNode.appendChild: Argument 1 is not an object.
in the re-insertion loop within updateContainer:I believe this occurs due to svelte 5's deep reactivity once again. If you have more then one x/y component the first component is destroyed / unmounted and the
component.destroyed
function is called, this triggers theupdateContainer
typescript function with one component still remaining, while this is occuring the other component is destroyed but is still present in theconfig.components
array, therefore this loop attempts to append an undefined object.The fix for this as far as my testing is doing
config.components = config.components?.filter((c) => !c.isDestroyed());
before calling updateContainer.The other problem is the component lifecycle action's
destroy
function is called before theline.svelte
onDestroy callback is called. Since theonDestroy
callback is responsible for marking the component as destroyed the lifecycle action doesn't remove the destroyed component.The text was updated successfully, but these errors were encountered: