docs: add eager consumption error to error-catalog.mdx (#2991)

Co-authored-by: yannik.peschke <[email protected]>
Co-authored-by: Zack Jackson <[email protected]>

Author: 3 people

apps/website-new/docs/en/guide/basic/error-catalog.mdx

@@ -107,3 +107,33 @@ In addition, the option `eager` encapsulates all shared-dependencies into a dedi
   }
 ```
 
+## Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'call')
+
+#### Error Message
+:::danger Browser Error Message
+Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'call')
+    at __webpack_require__ (builder-runtime.js:32:21)
+    ...
+:::
+
+:::danger Browser Error Message (Specific to Rspack)
+Undefined factory webpack/container/remote/`remote-name`/`name-of-exposed-file`
+:::
+
+#### Solution 1
+
+**Example scenario**: You have an npm package with `eager` remote imports (such as `import Button from 'myRemote/button'`) and share this npm package with `eager: true`.  
+**Example scenario**: You're sharing a mix of packages, some with `eager: true` and others with `eager: false`, and the `eager: true` packages import the `eager: false` shared packages.
+
+This error occurs when a remote (often a library-like shared module) contains unwanted circular dependencies between the `shared dependencies` of the remote and other consumers or the host application. If the environment is using the Module Federation config `shared: { "package-name": { eager: true } }`, the Rspack/Webpack builder runtime will break with this error.
+
+To resolve this, remove the `eager: true` option from the shared configuration of all connected remotes and the host application. This will prevent the shared dependencies from being eagerly loaded and will allow the remote to be loaded correctly.
+
+Since eager consumption wraps all dependencies inside the entry file of the remote, Rspack/Webpack cannot detect the specific handlers for each dependency, resulting in `undefined`.
+
+#### Solution 2
+
+You are missing an "async boundary" in your application. Ensure that you have a dynamic import at the top of the application.  
+For example, if your entry point is `index.js`, copy the contents of `index.js` into a new file called `bootstrap.js`. Then, in `index.js`, replace the code with `import('./bootstrap.js')`.
+
+Alternatively, you can try the hoisted runtime experiment, which removes the need for an async boundary in user code. Learn more here: [Hoisted Runtime Experiment](https://module-federation.io/configure/experiments.html#federationruntime).