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
{{ message }}
Repository navigation
Nested parcels gets unmounted multiple times and throws #164
I'm having a scenario where parcel A is mounted as <Parcel config={() => System.import('@parcelA')} /> in the main app and that parcel in turn mounts parcel B as <Parcel config={() => System.import('@parcelB')} />.
When parcel A then gets unmounted, parcel B will be unmounted twice. Once by componentWillUnmount in the Parcel component of parcel A here and once as the child of parcel A here.
One of these times parcel B already has the status "UNMOUNTING" here and will cause the error https://single-spa.js.org/error/?code=6&arg=&arg=UNMOUNTING to be thrown. Parcel A also will end up with status "SKIP_BECAUSE_BROKEN" and still be kept as a child parcel by the main app.
I'm having a scenario where parcel A is mounted as <Parcel config={() => System.import('@parcelA')} /> in the main app and that parcel in turn mounts parcel B as <Parcel config={() => System.import('@parcelB')} />.
When parcel A then gets unmounted, parcel B will be unmounted twice. Once by componentWillUnmount in the Parcel component of parcel A here and once as the child of parcel A here.
One of these times parcel B already has the status "UNMOUNTING" here and will cause the error https://single-spa.js.org/error/?code=6&arg=&arg=UNMOUNTING to be thrown. Parcel A also will end up with status "SKIP_BECAUSE_BROKEN" and still be kept as a child parcel by the main app.
Any workaround available for this? I'm also facing this issue although I'm simply using Parcel within a top-level Single-SPA app that unmounts together with the Parcel.
Activity
boringContributor commentedon Feb 24, 2023
How do you use the
Parcelcomponent inreact v5? This seems not even to work anymoreMilanKovacic commentedon Jan 5, 2024
There was an error in one of the published versions. It should be fixed now.
sandeeppatel344 commentedon Nov 21, 2024
I am also facing same issue.
How we can solve?
levrik commentedon Jul 18, 2025
Any workaround available for this? I'm also facing this issue although I'm simply using
Parcelwithin a top-level Single-SPA app that unmounts together with theParcel.