-
Notifications
You must be signed in to change notification settings - Fork 47.7k
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
Cannot read properties of undefined (reading 'getStackAddendum') #31606
Comments
Maybe you're mixing dev and prod? With module federation it's also easy to accidentally ship multiple Reacts. Without a minimal reproduction, we won't be able to help. |
federation.config.js in shell app
webpack.config.js in shell app
federation.config.js second app
webpack.config.js in second app
To avoid running multiple react and react-dom I use singleton: true |
This is not a minimal production. It needs to be stripped of all dependencies that don't contribute to the bug. So you'd strip code until it no longer reproduces. Then you can pack it into a cloneable repository with clear instructions how to reproduce. |
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! |
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you! |
After building the application on the production version I get the error Cannot read properties of undefined (reading 'getStackAddendum'). I have split the application into microfronts that are linked using the webpack module federation.
The error here is because ReactDebugCurrentFrame is undefined.
The problem does not appear in the dev version, only in the production version
package.json application shell
package.json second aplication
The text was updated successfully, but these errors were encountered: