-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[URGENT] react-toast is injected to DOM by default causes multiple web app using Style UI 2.x to fail on load #210
Comments
Try
|
Thanks @roth1002. Our team have tried this but didn't work. I've copied the email reply from the developer about this in case you didn't receive it:
|
As an update to the previous comment by @joyfulelement, I further extended the exact import to be used for each component and not just
Although, it makes code bit clumsy but it's a temporary fix for now to avoid injection of Toast element into the DOM. |
Resolved in 2a90d3f It will be available in v0.8 or a later release. |
Fixed in 0.8.0 |
Business Impact
Problem
Root Cause
react-toast
component is injected to DOM by default when using Styled UI even if web application doesn't use Toast component.Effect & Impact
This becomes an issue if we dynamically mount and unmount microfrontend web apps (e.g. with single-spa) that uses Styled UI, as single-spa is the container for it.
<body>
element in DOM is littered with instance ofreact-toast
element injected from last microfrontend web apps using Styled UIReproduced Steps
The reproduced steps are very simple and captured on the internal JIRA, since it's causing an incident and impacting our production environment, those details are only shared within the JIRA case. Please consult @ultralabed for detail.
Proposed Solutions
Workaround
However, without the proper fix (as proposed below) the of root cause, the problem will against resurface if multiple web app begin using Toast component.
Proper Fix on the Root Cause
OR
The text was updated successfully, but these errors were encountered: