NextFederationPlugin: Setting name: 'main' causes unexpected error

[mshan-mrt]

Hi, I’m using @module-federation/nextjs-mf’s NextFederationPlugin in a Next.js application, and I encountered an issue when setting the name property to 'main'.

Here’s a simplified version of my plugin configuration:

const NextFederationPlugin = require('@module-federation/nextjs-mf');

module.exports = {
  plugins: [
    new NextFederationPlugin({
      name: 'main',
      filename: 'static/chunks/auth.js',
      remotes: {
        remote: `remote@${path}/remote-build/${process.env.TARGET_ENV}/_next/static/chunks/remote.js`,
      },
    }),
  ],
};

As soon as I set name: 'main', I get an error (see attached image). The error message suggests adding the eager option, but even after setting eager: true, the error does not go away.

However, if I change the name to something else (for example, 'home'), the error disappears immediately and everything works as expected.

It seems like 'main' may be a reserved or conflicting value either within Webpack or the Next.js Module Federation integration. Has anyone else experienced this? Is there a technical reason why 'main' shouldn’t be used as a name?

Any insights or explanations would be greatly appreciated.

Thanks in advance! 🙏

[ScriptedAlchemy]

check if window.main is something in a standard next app

[ScriptedAlchemy]

Might be that the a chunk name called 'main' exists, causing a collisison