Native Federation 18.1

Changes

• Use the official private API in @angular/build so that we don't need to patch this package anymore. This resolves several issues.
• Add migration guide for migrating from Module Federation to readme
• Add hash to generated bundle names to prevent situations where several bundles get the same name
• Allow ng build --base-href /my-base-path/
• Fix: Make sure the process exits when there is an error

Native Federation 17.1.

CLI-Integration

Since 17.1, Native Federation for Angular uses the Angular CLI's esbuild-based Application Builder and the CLI's Dev Server to keep track with all the innovations and performance-improvements in that space.

Native Federation 16.3

Performance 🚀

This release brings tremendous performance improvements due to:

• calling esbuild less often with more coarse-grained tasks
• Not writing files to disk in dev mode

This brings the excellent performance known by Angular's esbuild builder this package currently delegates to.

Remove Schematic

You can now remove the native-federation config with the new remove schematic:

ng g @angular-architects/native-federation:remove --project xyz

Details & Tutorial

https://www.npmjs.com/package/@angular-architects/native-federation

15.0.0

@angular-architects/module-federation 15.0.0

• Updated for Angular 15
• npm run run:all now also works in an Nx workspace
• New skip config property for skipping shared mappings, shared deps, and secondary entry points
• loadRemoteModule defaults to type: 'manifest' if there was a manifest loaded
• New initFederation function as an alternative for both, loadManifest and setManifest. Also, this provides feature parity with Native Federation
• The init schematic now generates a call to initFederation (i/o loadManifest) when using the flag --type dynamic-host

14.3.0

14.3.0 - Angular 14 Support & More

Update

This library supports ng update:

ng update @angular-architects/module-federation

If you update by hand (e. g. via npm install), make sure you also install a respective version of ngx-build-plus (version 14 for Angular 14, version 13 for Angular 13, etc.)

Breaking Changes

• shareAll now uses the DEFAULT_SKIP_LIST by default.

Features

• add withModuleFederationPlugin to simplify the generated (ca26aeb)
• mf-runtime: load remotes in parallel (5615917)
• mf-runtime: supporting mf manifests (64ec2dc)
• mf: add support for eager and pinned (623837c)
• mf: add type option to ng-add (c57d87f)
• mf: dev-server (run:all) accepts project names via command line args (b765515)
• mf: respect APF v14 for discovering secondaries (00344c2)

Documentation

• update readme and tutorial for v14.3 (fbdb463)

14.2.0

• fix: Use "number" for port parameter during init #147
• feature: new appType makes bootstrap helper automatically call shareNgZone or connectRouter. No need to call it in the AppComponent by hand. See usage in the updated readme

14.1.1

• fix: install ngx-build-plus via schematic to avoid issues with yarn (commit)

14.1.0

• feat: connectRouter: add query params support #119
• feat: provide DEFAULT_SKIP_LIST constant for shareAll
• fix: also update local tsconfig.app.json if target doesn't fit
• fix: Property 'port' does not match the schema. '3000' should be a 'number #132
• docs: typo in readme and adjust typing of shareAll #117
• security: update node-fetch

Version 14

Updated for Angular CLI 13.1

• Important: Use CLI 13.1

• Details for Migration and API changes:
  https://github.com/angular-architects/module-federation-plugin/blob/main/migration-guide.md

12.5.0

Nx Support

ng add now uses Nx builders for Nx workspaces. To detect if an Nx workspace is used, the schematics basically look out for an nx.json. You can also control this behavior by hand using the --nx-builders switch now supported by ng add (e. g. --nx-builders false).

Testing

The ng add schematic is not changing the test config in your angular.json anymore to prevent issues with eager bundles and webpack module federation.

Consequences:

• Remotes: No issue
• Hosts: Should be tested with E2E tests