Describe the feature you'd like to request

Make sure that react is shared via webpack share scopes when module federation is active.

When using a sidecar build(webpack plugin that creates a third build for any expose modules) https://github.com/module-federation/nextjs-mf

You can inspect the code and see how I've been able to make it work with a loader-plugin combo

Describe the solution you'd like

I was able to put the following in _app

if (process.browser) {
  // share something & consume it to ensure the share scope is initialized
  import('@module-federation/nextjs-mf/lib/noop')
  // or manually initialise it by uncommenting below
  //try {
  //  __webpack_init_sharing__('default');
  //} catch (e) {
  //}

  Object.assign(__webpack_share_scopes__.default, {
    "next/link": {
      [next.version]: {
        loaded: true,
        get: () => Promise.resolve(() => require("next/link")),
      },
    },
    "next/head": {
      [next.version]: {
        loaded: true,
        get: () => Promise.resolve(() => require("next/head")),
      },
    },
    "next/dynamic": {
      [next.version]: {
        loaded: true,
        get: () => Promise.resolve(() => require("next/dynamic")),
      },
    },
  });
}

and share React eagerly with MF plugin

      config.plugins.push(
        new webpack.container.ModuleFederationPlugin({
          remoteType: "var",
          remotes: {
            next1: "next1",
          },
          shared: {
            react: {
              // Notice shared ARE eager here.
              eager: true,
              singleton: true,
              requiredVersion: false,
            },
          },
        })
      );

After upgrading to next 11 and react 17, i was no longer able to use eager:true to share react properly from nextjs, I end up getting hooks errors (more than one react instance is getting initialized)

I was able to work around the problem by adding this object to the "shimmed" share scope, however I'm unable to utilize the nice import('otherapp/moduleIwant') because webpack errors saying that react cannot be found on share scope, likely due to import hoisting and the fact that I'm assigning share scope later on in the app boot sequence.

    "react": {
      [require('react/package.json').version]: {
        loaded: true,
        get: () => Promise.resolve(() => require("react")),
      },
    },

By shimming react into share scope, I'm able to use federated modules but only if I am using the low-level window.scope.get(someModuleIwant);

You can see a full example (in broken state) here https://github.com/module-federation/module-federation-examples/tree/master/nextjs

Run yarn in the monorepo root, then yarn in the /nextjs folder, then yarn start and visit localhost:3001 and you'll see hooks errors.

If next could internally eager share react or wrap its entrypoints behind a dynamic import (before react is first imported) then it would work.

Describe alternatives you've considered

I own the alternatives :P tried everything