single-spa-angular: Problems with mounting the same parcelConfig multiple times
Demonstration
const parcelConfig = singleSpaAngular({...})
const parcel1 = mountRootParcel(parcelConfig, {...})
const parcel2 = mountRootParcel(parcelConfig, {...})
Expected Behavior
When you mount the same single-spa-angular parcelConfig multiple times, multiple independent parcels should be created.
Actual Behavior
When you mount the same single-spa-angular parcelConfig multiple times, only one of them really works. See more at https://single-spa.slack.com/archives/CGETM8T5X/p1593605815279300
This is caused by the opts object being shared between the parcels, but it containing singleton properties. The properties should be changed to be objects/arrays that allow for multiple values (one for each parcel). Specifically opts.bootstrappedModule should not be a single value, but an array/object with multiple values.
This bug also existed in single-spa-react and was fixed in https://github.com/single-spa/single-spa-react/pull/68. The history of it is that many of the single-spa helper libraries were authored at a time when only single-spa applications existed, instead of parcels. Applications are indeed singletons, which is why there is no issue for them.
About this issue
- Original URL
- State: open
- Created 6 years ago
- Comments: 19 (6 by maintainers)
I was able to solve the given problem with no changes to the library.
Working with single-spa-react, my team and I encountered an issue where we couldn’t instantiate multiple parcels on the same page using another parcel as a wrapper. After conducting extensive research, we discovered that using the
wrapWithprop of the Parcel component, as described in the single-spa-react documentation, resolved the problem. By wrapping our parcels with a simple div, we were able to successfully instantiate multiple identical parcels inside a parcel wrapper without any issues.I believe that our solution using
wrapWithin single-spa-react could contribute some ideas to address the problem, or at least prompt an exploration of thewrapWithprop.I solved this problem changing the name of the selector main of my apps, for example I used
I had this in main.single-spa.ts
I changed this for
and I changed the selecctor name too (app.component.ts)
now
and for last I changed the index.html
now
This error happend 'cause single-spa can’t use the same parcelId with multiple parcelConfigs, you need to have a unique parceId per application