Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Async modules not resolved correctly with module federation
See original GitHub issueBug report
What is the current behavior? async modules (e.g. using top-level-await) are resolved into promise by Module Federation
If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/vincenthend/webpack-module-federation-async-modules
Repo above is two webpack apps using module-federation
main-app is importing a function from component-app, where there is a top-level-await in the imported module.
The imported module is resolved as Promise instead of object (even if using import syntax)
What is the expected behavior? Imported modules from module federation should resolve normally whether it’s async modules or not
Other relevant information: webpack version: 5.61.0 Node.js version: 14.8 Operating System: macOS 10.15 Additional tools: -
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
When working with async modules you need to make sure that your are working only with ESM imports. And also make sure to not accidentically transpile them (via babel) to CommonJs (as shown in the screenhot,
(0, _utils).hasRoleis how babel transpiles imports)Imported modules from module federation should resolve normally whether it’s async modules or not
I have the same problem, it seems to be a bug?