module-federation-examples: Exposed modules stops working with default webpack 5 optimizations runtimeChunk: 'single'

@Guriqbal-Singh-Alida Please keep that repo up as is if possible until the plugin can be documented somewhere else. Good job on finding a fix 🎉

For others, this is a plugin that merges the runtimes to get around runtimeChunk: single https://github.com/Guriqbal-Singh-Alida/basic-remote-runtime-single/blob/master/apps/app2/plugins/moduleFedSingleRuntime.js

@Guriqbal-Singh-Alida @maraisr said he would look into it. We are scattered throughout the world though and have day jobs, please be patient. 😄

@Guriqbal-Singh-Alida, I think @ScriptedAlchemy will pull this into the MF org for others to use.

That is very elegant @Guriqbal-Singh-Alida. Good job.

@jacob-ebey i pushed new changes to optimize so that we don’t create an extra file. Also previous solution had a limitation where it did not worked when ran in dev mode, it required the files to be in build folder. Overall please check the new solution. Also probably will create it as plugin unless WMF folks advice otherwise. if possible please update your above comments based on new solution.

//Reference: https://github.com/module-federation/nextjs-mf

const ConcatSource = require('webpack-sources/lib/ConcatSource');

module.exports = class ModuleFedSingleRuntimePlugin {
  constructor(options) {
    this._options = {fileName: 'remoteEntry.js', ...options};
  }
  // Define `apply` as its prototype method which is supplied with compiler as its argument
  apply(compiler) {
    if (!this._options) return null;
    const options = this._options;

    // Specify the event hook to attach to
    compiler.hooks.emit.tap("EnableSingleRunTimeForFederationPlugin", (compilation) => {
      const { assets } = compilation;
      const runtime  = assets['runtime.js'];
      const remoteEntry = assets[this._options.fileName];
      const mergedSource = new ConcatSource(runtime, remoteEntry);
      assets[this._options.fileName] = mergedSource;
    });
  }
};

But to add; feels that https://github.com/webpack/webpack/pull/11843 should be merged in order to resolve the issue in package itself. It is hanging there from quite a while

@Guriqbal-Singh-Alida, does your company know about sponsors? If it’s something that want quick responses on, I’d honestly point then at sponsoring the webpack organization or Tobias at a level where he would dedicate time for your problems. Let them know if they want people working for them, they should pay them. Otherwise I’d let them know tasks will carry as no one else here cares about their goals or priorities.