fix: #156 ssr: require is not defined

[poenneby]

Further to this discussion: #156 (comment)

[gioboa]

Thanks @poenneby for your help 🤗

[poenneby]

@gioboa Running the multi-example with these changes correctly export default exportModule but at runtime I get "unexpected token: default"
Tracing this back in the code the export default gets incorrectly identified as a named export in src/plugins/pluginDevProxyModuleTopLevelAwait.ts

The transpiled code that causes the error:

// node_modules/__mf__virtual/host__loadRemote__remote_mf_1_Product__loadRemote__.js
var import_node_module = __toESM(require_node_module());
var { loadRemote } = require2("@module-federation/runtime");
var { initPromise } = require2("__mf__virtual/host__mf_v__runtimeInit__mf_v__.js");
var res = initPromise.then((_) => loadRemote("remote/Product"));
var exportModule = (
  /*mf top-level-await placeholder replacement mf*/
  initPromise.then((_) => res)
);
var require2 = (0, import_node_module.createRequire)(import.meta.url);
var host_loadRemote_remote_mf_1_Product_loadRemote_default = exportModule;

              const __mfproxy__awaitdefault = await default(); <-- HERE
              const __mfproxy__default = () => __mfproxy__awaitdefault;
            
export { __mfproxy__default as default };

Any ideas?

[gioboa]

I see, I will check it. Thanks for the deep investigation

[rafal-akiro]

Hey @gioboa any update on this?

[gioboa]

I did look at it yet. But eventually we can continually change the code if an SSR env is detected