Wrapper library around @module-federation/enhanced breaks the federation runtime

[VanTigranyan]

Hi. I have the code below, that dynamically loads the remotes' definitions and calls init(). Also, if the same function is called from a subsequent MFE, remotes are already assigned to a global var, allowing the request to be skipped. Now, if I use this function directly in my host app, there is no issue; it works perfectly well, but when I move this to a small library (so that the code can be shared), build it, and import it, then I get the error in the screenshot. Is the build that breaks it, or should the init() function not be wrapped in general at all? Thanks a lot in advance.

export const printMFELog = (message: string, data: any = '') => {
  console.info(`%c ${message}`, 'background: black; color: orange', data);
};
export const loadRemotesDefinitions = async (
  mfeName: string,
  debugEnabled = false,
) => {
  if (debugEnabled) {
    printMFELog(
      `[FSN MFE] Loading MF manifest for lane ${getLane().toUpperCase()}`,
    );
  }
  let remotes;
  if (window.remotes) {
    remotes = window.remotes;
  } else {
    remotes = await fetch(
      `https://mfe.example.com/manifest/dev/remotes.json`,
    )
      .then((res) => res.json())
      .catch((e) => console.error('Failed to load MF manifest:', e));
  }
  if (debugEnabled) {
    printMFELog('[FSN MFE] Loaded MF manifest:', remotes);
  }
  init({
    name: mfeName,
    remotes,
  });
};

[ScriptedAlchemy]

Provide a repo so we can inspect it