-
-
Notifications
You must be signed in to change notification settings - Fork 371
Open
Description
Describe the bug
When resolveRequest flag is passed inside a consumer metro.config.js, this function is not being passed and called inside the metro core package.
Example: config
const config = {
resolver: {
useWatchman: false,
resolveRequest: (context, moduleName, platform) => {
console.log('[Custom Resolver] Resolving:', moduleName); // <---- this line is not called
return context.resolveRequest(context, moduleName, platform);
},
},
Reproduction
https://github.com/module-federation/metro
Used Package Manager
pnpm
System Info
System:
OS: macOS 15.6.1
CPU: (14) arm64 Apple M4 Pro
Memory: 1.32 GB / 48.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.17.0 - /Users/trozee/.nvm/versions/node/v22.17.0/bin/node
npm: 10.9.2 - /Users/trozee/.nvm/versions/node/v22.17.0/bin/npm
pnpm: 8.11.0 - /Users/trozee/.nvm/versions/node/v22.17.0/bin/pnpm
bun: 1.2.19 - /Users/trozee/.bun/bin/bun
Deno: 2.5.6 - /Users/trozee/.deno/bin/deno
Watchman: 2025.06.30.00 - /opt/homebrew/bin/watchman
Browsers:
Brave Browser: 142.1.84.132
Chrome: 142.0.7444.176
Safari: 18.6Validations
- 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