-
-
Notifications
You must be signed in to change notification settings - Fork 358
Open
Description
Describe the bug
Bug description
- For remote App, I set webpack entry as an empty object
- the build will failed for no matched module factory for EntryDependency


Bug Reason
- For webpack EntryOptionPlugin, when entry is empty, EntryPlugin will not be applied. So normalModuleFactory will not be bound for EntryDependency.
- In ContainerEntryModule, an EntryDependency is used for building runtime entry.



Reproduction
https://github.com/xinyuehtx/module-federation-error
Used Package Manager
pnpm
System Info
System:
OS: macOS 15.5
CPU: (11) arm64 Apple M3 Pro
Memory: 208.41 MB / 36.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.16.0 - ~/.nvm/versions/node/v20.16.0/bin/node
npm: 10.8.1 - ~/.nvm/versions/node/v20.16.0/bin/npm
pnpm: 9.15.4 - ~/.nvm/versions/node/v20.16.0/bin/pnpm
Browsers:
Chrome: 138.0.7204.169
Safari: 18.5
Validations
- Read the docs.
- Read the common issues list.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Make sure this is a Module federation issue and not a framework-specific issue.
- The provided reproduction is a minimal reproducible example of the bug.
Metadata
Metadata
Assignees
Labels
No labels