nx/docs/shared/recipes/module-federation-with-ssr.md

Setup Module Federation with SSR for Angular and React

This guide will walk you through creating a Module Federated setup with Server Side Rendering (SSR) for Angular and React using Nx and its generators.

Steps

Create an empty workspace

Run the following command with the options listed to create an empty workspace.

NX   Let's create a new workspace [https://nx.dev/getting-started/intro]

✔ Which CI provider would you like to use? · skip
✔ Would you like remote caching to make your build faster? · skip

{% card title="Opting into Nx Cloud" description="You will also be prompted whether to add Nx Cloud to your workspace. We won't address this in this recipe, but you can see the introduction to Nx Cloud for more details." url="/ci/intro/ci-with-nx" /%}

Install your framework plugin

{% callout type="note" title="Keep Nx Package Versions In Sync" %} Make sure to install the @nx/angular or @nx/react versions that matches the version of nx in your repository. If the version numbers get out of sync, you can encounter some difficult to debug errors. You can fix Nx version mismatches with this recipe. {% /callout %}

{% tabs %}

{% tab label="Angular" %}

{% /tab %}

{% tab label="React" %}

{% /tab %}

{% /tabs %}

Generating a host and multiple remotes with SSR

We will generate the apps required for a storefront application.
We will need the following applications:

• Store - host application
• Product - remote application
• Checkout - remote application

Nx allows you to do this with a single command:

{% tabs %}

{% tab label="Angular" %}

{% /tab %}

{% tab label="React" %}

{% /tab %}

{% /tabs %}

This will generate three applications, set up with SSR and Module Federation.

Serving the store application

When using Module Federation, we want to serve the host application along with the remote applications so that everything works as expected.

To do this, run:

{% tabs %}

{% tab label="Angular" %}

{% /tab %}

{% tab label="React" %}

{% /tab %}

{% /tabs %}

This will run all three application servers but only the store will be watching for file changes. If you make a change to one of the remote applications (checkout or product) the changes will not be hot reloaded.

Serving the store application with file watching for checkout

If working on a remote application, we can still serve it via the host application and have it watch for changes.

To serve the store application and watch for changes on the checkout application run:

{% tabs %}

{% tab label="Angular" %}

{% /tab %}

{% tab label="React" %}

{% /tab %}

{% /tabs %}

Additional Resources

To learn more about Module Federation, we have some resources you might find useful:

• Concepts: Nx Module Federation Technical Overview
• Guide: Faster Builds with Module Federation
• Video: Speed up your Angular serve and build times with Module Federation and Nx