Not possible to extract MF dynamic loading code to util library

In order to dynamically load remote modules I have created the following “importRemote” function:

import script from "scriptjs";

const loadEntryPoint = url =>
  new Promise(resolve => {
    script.urlArgs(`t=${new Date().getTime()}`);
    script(url, () => resolve());
  });

// Dynamically import a remote module using Webpack's loading mechanism:
// https://webpack.js.org/concepts/module-federation/
const importRemote = async (url, scope, module) => {
  if (!window[scope]) {
    //Get the remote entry point:
    await loadEntryPoint(`${url}/remoteEntry.js`);
    if (!window[scope]) {
      return Promise.reject(new Error(`${scope} could not be located!`));
    }
    // Initializes the share scope. This fills it with known provided modules from this build and all remotes
    await __webpack_init_sharing__("default");
    // Initialize the container, it may provide shared modules
    await window[scope].init(__webpack_share_scopes__.default);
  }

  const moduleFactory = await window[scope].get(
    module.startsWith("./") ? module : `./${module}`,
  );
  return moduleFactory();
};

export default importRemote;

I use this like React.lazy(()=>importRemote(url, scope, module))

This code is used in several projects so I want to extract the importRemote module to an external util library but I can’t because __webpack_init_sharing__ and __webpack_share_scopes__ are compilation scope variables from the project in which the module is located. If I move this code to a library and import it from there it doesn’t work because it seems that the scope variables are taken from the library’s build instead. Is there a way to achieve this?

[ScriptedAlchemy]

I currently have all dynamic loading abstracted to a npm package. Build it with Babel or something standard. It should work

[ScriptedAlchemy]

Make npm package a webpack build itself. Then it loads its own remote as needed if you don’t register the remote in your main build