Modern.js Module Federation SSR example outdated

[YanPes]

I want to migrate Modern.js Module Federation to SSR.

Is this example still valid? modernjs-ssr-example

The package @modern-js/runtime/mf seems to not exist anymore.

I did find out that @module-federation/modern-js/runtime contains createRemoteSSRComponent.

When running it the error log spits out:

SyntaxError: Function statements require a function name
    at new Function (<anonymous>)
    at getTargetModuleInfo (createRemoteSSRComponent.js:39:1)
    at collectSSRAssets (createRemoteSSRComponent.js:70:1)
    at createRemoteSSRComponent.js:123:1
    at step (tslib.es6.mjs:147:1)
    at Object.next (tslib.es6.mjs:128:1)
    at asyncGeneratorStep (_async_to_generator.js:3:1)
    at _next (_async_to_generator.js:20:1) Error Component Stack
    at fallback (layout.tsx:16:1)
    at default (<anonymous>)
    at Suspense (<anonymous>)
    at ErrorBoundary (react-error-boundary.development.esm.js:12:1)
    at createRemoteSSRComponent.js:176:1
    at SnackbarProvider (SnackbarProvider.js:9:1)
    at Layout (layout.tsx:27:1)
    at RenderedRoute (hooks.tsx:658:1)
    at RenderErrorBoundary (hooks.tsx:584:1)
    at DataRoutes (index.tsx:768:1)
    at Router (components.tsx:420:1)
    at RouterProvider (index.tsx:491:1)
    at plugin.js:116:1
    at AppWrapper (<anonymous>)
    at WithCallback (withCallback.js:3:1)
    at SSRApp (<anonymous>)

Did the package just move over or do we have a new way of dealing with MF-SSR in Modern.js in genreal?

Thank's guys!

[Nsttt]

Have a look at https://github.com/module-federation/core/tree/main/apps/modernjs-ssr :)

[YanPes]

I checked it. Thank you for the reply! The only real difference is the lazy import instead of the "ssrcomponent" wrapper.
This does resolve the error message but not the ssr rendering issue.
Everything runs "ssr" just the module federation chunk is hydrated afterwards, which makes sense since it is wrapped in a Suspense and lazy load configuration on the provided example.

Side info: I am running everthing inside a Kubernetes cluster. The "port" key in the modern.config.ts is not set on my side. This is handled via the docker port distribution anyways.

Any ideas?

[YanPes]

After stripping down all complexity and removing the docker-compose configuration the issue still persists. Error message is now a bit more meaningful:

@2heal1 : Since you worked on the example pages for modern.js ssr, any idea?