【Module Federation】Error loading module - Cannot read property 'call' of undefined

[YD-Feng]

Bug report

What is the current behavior?
1.【dbcWebMain】app exposes some modules
2. webpack.config.js set optimization.runtimeChunk: 'single' for HMR work
3. HMR work well，but 【dbcWebSub】app Error loading module
4. if webpack.config.js set optimization.runtimeChunk: false，modules load success，but HMR not work

repository：
https://gitee.com/caozhifeng1000/webpack-5-demo.git

start app：
npm run dev

【dbcWebMain】app run at http://127.0.0.1:3927
【dbcWebSub】app run at http://127.0.0.1:4936

Other relevant information:
webpack version: 5.51.1
webpack-cli version: 4.8.0
webpack-dev-server version: 3.11.2
Node.js version: 14.16.1
Operating System: Win10

[webpack-bot]

For maintainers only:

• webpack-4
• webpack-5
• bug
• critical-bug
• enhancement
• documentation
• performance
• dependencies
• question

[YD-Feng]

/******/ // Execute the module function /******/ try { /******/ var execOptions = { id: moduleId, module: module, factory: __webpack_modules__[moduleId], require: __webpack_require__ }; /******/ __webpack_require__.i.forEach(function(handler) { handler(execOptions); }); /******/ module = execOptions.module; /******/ execOptions.factory.call(module.exports, module, module.exports, execOptions.require); /******/ } catch(e) { /******/ module.error = e; /******/ throw e; /******/ }

execOptions.factory is undefined

[franckXu]

https://webpack.js.org/blog/2020-12-08-roadmap-2021/#hot-module-replacement-for-module-federation

[alexander-akait]

Change name in package.json on different names, it was answered a lot of time

[alexander-akait]

And we already work on our docs about it

[deepsweet]

Could you please elaborate? I have the same error appearing if I import a federated module statically instead of dynamically.

[GVLevi]

If it was "answered a lot of times" then surly there's a place with documentation you can link to. A vague comment doesn't provide any insight as to what the underlying issue is or why it's occurring - so for those where the name differs and changing it in package.json doesn't fix it your comment provides no better context for individual resolution.

[JonWallsten]

@alexander-akait This issue started appearing for us after updating from:

"webpack": "5.64.2",
"webpack-cli": "4.9.1",
"webpack-dev-server": "4.5.0"

to:

"webpack": "5.67.0",
"webpack-cli": "4.9.2",
"webpack-dev-server": "4.7.3"

Have you guys done any recent changes related to this?

It's trying to load module 78.
But it doesn't exist:

It does however exist in the cache:

I'll work on a repro if necessary. Just wanted to give you a quick heads up!

It only appears in one of our 5 applications with nearly identical setup.

[vankop]

@alexander-akait should this be treated as bug?

[alexander-akait]

Need to look at code, maybe it is async loading CSS in initial chunk

[JonWallsten]

@alexander-akait You still have access to the repo since way back. I merged the branch to master to get the new dependencies. So if you want to look at the code you can check the master branch.

[corradin]

My issue was that I was missing a dynamic import. I renamed the existing index.js (I had an existing repo) to bootstrap.js, added a new index.js file with the line import('./bootstrap');

[vedikak]

Hi
I am facing the same challenge, is a conclusive solution reached? I havent been able to fix the execOptions error yet