Error: Container missing while loading ... while running `next start` but not on `next dev`
See original GitHub issueWhile running app through yarn start
or next start
. I get error on runtime saying
Error: Container missing
while loading "./NAME_OF_COMPONENT` from ....
But this does not happen while running on development mode
yarn dev
or next dev
This was also mentioned here: https://github.com/module-federation/module-federation-examples/issues/680
Any ideas? Is this known issue or is there anything that we are missing?
Thank you!
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
NextJS example: dev build works, "yarn serve" does not #680
Hey, I am struggling to get the production build of a federated NextJS application to work. It works fine in development mode, but...
Read more >I am getting error while converting my next js project to ...
I made node version 14, I deleted next js from package.json file and after npm install in Dockerfile I added this command RUN...
Read more >Advanced Features: Error Handling
It is a modal that covers the webpage. It is only visible when the development server runs using next dev , npm run...
Read more >Troubleshooting
Troubleshooting. This section attempts to outline issues that users frequently encounter when first getting accustomed to using React Navigation.
Read more >Known issues with Android Studio and Android Gradle Plugin
This error occurs on Linux-based platforms when starting the native debugger. It indicates that one of the libraries required by the native debugger...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
these errors may be related to previous breaking changes in my example application. Next has undergone some updates and I’ve updated the sample and pluign to reflect that. - serverside I’m not able to get react sharing to work properly, so I’ve had to make it conditional for process browser. Just check the example and you’ll see how I’ve configured it. If anyone has ideas on getting federated serverside to not throw the multiple react error, then colocated SSR would work
Following up on my previous comment, I realize my screenshot shows a different error from what this ticket reports. It turns out I was experiencing a timing issue that sometimes results in the
next1 is not defined
error, but if I either remove theasync
attribute from the script tag, or enable network throttling (ex. Fast 3G), theContainer missing
error is reproducible every time: