Chrome Extension is not working due to empty moduleInfo

[benmarch]

Describe the bug

I just upgraded my NextJS MFEs to MF 2.0 and everything is working as expected. I installed the Chrome Extension to test out the proxy functionality, but it just shows an icon and "No ModuleInfo Detected".

I looked through the source code and found this line in the devtool package that looks for window.__FEDERATION__.moduleInfo:

core/packages/chrome-devtools/src/App.tsx

Line 21 in 8941ef4

const [module, setModule] = useState(window.__FEDERATION__?.moduleInfo || {});

I can confirm that it's empty in the browser console:

I can also confirm that it's empty in the nextjs-ssr example app: https://github.com/module-federation/module-federation-examples/tree/master/nextjs-ssr

Just wondering if I'm missing some config to enable it, or if it's a bug.

Reproduction

https://github.com/module-federation/module-federation-examples/tree/master/nextjs-ssr

Used Package Manager

npm

System Info

System:
    OS: macOS 13.6.7
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 530.61 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.19.1 - /usr/local/bin/node
    npm: 10.2.4 - /usr/local/bin/npm
    pnpm: 8.15.2 - /usr/local/bin/pnpm
  Browsers:
    Chrome: 126.0.6478.127
    Safari: 16.6

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.

[ScriptedAlchemy]

Next doesnt support most of the new ecosystem. Youd need to use the json protocol for remotes and currently i dont think next works with the json protocol / havent tried

[benmarch]

Ah ok gotcha, thanks! I'll close this out, but I might try to get that working locally

[benmarch]

I was able to get this working by making some changes to my runtime plugin. I opened a PR with similar changes in case you want to incorporate them; should be a non-breaking change: #2726