@angular-architects/module-federation

• Readme for Module Federation
• Readme for Native Federation

[!WARNING] Native federation has moved!

This is our older deprecated v3 version. Starting Angular 22, we're moving to a new repository. For upgrading from v3 to v4, please have a look at our new repository.

Local Development

Playground App

You can test directly the libraries by using the playground application:

1. Start the host application: shell npx nx run playground:serve
2. Start the remote application: shell npx nx run mfe1:serve --port 3001

By using that approach you can test your modifications on the libraries.

Test Library on external repository

If you want to test the modifications directly on your application, you can follow the steps:

1. Start the local registry Verdaccio: shell npx nx run local-registry

2. Then you can publish the libraries by using:

3. For Module federation: shell npm run publish-local:mf

4. For Native federation:

shell npm run publish-local:nf

This will first build the libraries and publish them to http://localhost:4873

1. Then just re-run the install on the other repo with you favorite package manager.

By default, the version from the package.json will be used. However, you can provide the version for a specific library by using:

npx nx run native-federation:publish-local -- --ver=17.0.8

Publish Libraries

Follow these steps to publish all libraries on npm:

• For Module federation: shell npm run publish:mf
• For Native federation: shell npm run publish:nf This will first build the libraries and publish them to npm registry.

By default, the version from the package.json will be used and the tag will be next. However, you can provide the version and the tag for a specific library by using:

npx nx run native-federation:publish -- --ver=17.0.8 --tag=latest