Skip to content

Angular MFE prerequisites: the Angular 22 toolchain

By the end of this page your machine can create, build and serve an Angular 22 shell and remote with Native Federation, and you know which extra packages the webpack Module Federation path needs. This is the only page in the section that lists versions; the other pages link here instead of repeating them.

The table reflects the npm registry on 2026-11-13. Re-check with npm view <package> version peerDependencies before you pin anything, because the federation packages track Angular minors closely.

Tool or package Version used in this section Why it matters
Node.js 22.22.3 or later 22.x, 24.15.0 or later 24.x, or 26.x Angular 22 supports ^22.22.3 || ^24.15.0 || ^26.0.0
npm Bundled with Node.js (examples were run with npm 10.9) Installs and runs the CLI
TypeScript 6.0.x (>=6.0.0 <6.1.0) Required range for Angular 22; ng new pins ~6.0.2
@angular/cli 22.2.7 Creates workspaces and runs builders
@angular/build 22.2.x esbuild application builder and dev server
@angular-architects/native-federation 22.2.5 Recommended federation path; peer dependency @angular/build ~22.2.0
es-module-shims Added by the Native Federation schematic (^2.8.0) Import map polyfill used in shim mode
@angular-architects/module-federation 22.0.0 Only for the webpack Module Federation path
@angular-builders/custom-webpack 22.x (22.0.1 at the time of writing) Webpack builder used by the Module Federation package from Angular 22 on
Git Any current release One repository per team, or one monorepo
Azure CLI (optional) Current release Only for Azure deployment

Two facts in that table trip people up:

  • Native Federation versions follow Angular major and minor. The adapter’s README says to use the release that matches your Angular major and minor (for example 22.1.x for Angular 22.1). Its peer dependency on @angular/build ~22.2.0 means version 22.2.5 expects Angular 22.2. If you upgrade Angular to 22.3, upgrade the adapter in the same change.
  • ngx-build-plus is no longer part of the webpack path. Up to Angular 21, @angular-architects/module-federation injected its webpack config through ngx-build-plus. From Angular 22 it uses @angular-builders/custom-webpack, and ng update migrates existing workspaces. Older tutorials that install ngx-build-plus with Angular 22 are out of date.

Federation is not part of Angular. Both federation packages are community projects maintained by Angular Architects and contributors; see Introduction for who provides which piece.

Use a version manager so each repository can pin its own Node.js version. With nvm on macOS or Linux:

Terminal window
nvm install 24
nvm use 24
node --version

On Windows, use nvm-windows, fnm or the official installer from nodejs.org. Add an .nvmrc (or the engines field in package.json) to every MFE repository so local machines and CI agree:

24

Verify: node --version prints a version inside the supported ranges above. Odd-numbered Node.js releases and old LTS lines (18, 20) are not supported by Angular 22.

You do not need a global CLI. Running a pinned version through npx avoids “works on my machine” problems when teams upgrade at different times:

Terminal window
npx @angular/cli@22 version

If you prefer a global install for convenience:

Terminal window
npm install -g @angular/cli@22
ng version

Verify: the output includes Angular CLI: 22.x and your Node.js version. Inside a workspace, ng version also lists @angular/build and typescript, but not the federation package; check that with npm ls @angular-architects/native-federation. Comparing both outputs between the shell’s and the remote’s repositories is the quickest way to spot a mismatch.

Step 3: Check TypeScript inside a workspace

Section titled “Step 3: Check TypeScript inside a workspace”

You do not install TypeScript globally for Angular work. ng new adds it as a dev dependency in the supported range. After creating a workspace (next page), confirm:

Terminal window
npx tsc --version

Verify: the version starts with 6.0. If an older global tsc is first on your path, the npx form still uses the workspace copy.

Step 4: Know which federation packages you will add

Section titled “Step 4: Know which federation packages you will add”

You add the federation package per workspace, not globally, as part of project setup. For the recommended path:

Terminal window
npm install -D @angular-architects/native-federation@22.2.5

The package’s init schematic then adds es-module-shims and the @softarc/native-federation-orchestrator runtime it depends on. For the webpack path, the ng add @angular-architects/module-federation schematic installs @angular-builders/custom-webpack for you; see Webpack Module Federation.

Verify: npm view @angular-architects/native-federation@22.2.5 peerDependencies prints @angular/build: '~22.2.0', matching the Angular minor you plan to use.

  • Visual Studio Code with the Angular Language Service extension gives template type checking and navigation. ng new generates .vscode/launch.json and tasks.json for debugging ng serve and ng test.
  • A Chromium-based browser or Firefox with developer tools. You will use the Network panel to inspect federation.manifest.json, remoteEntry.json and importmap.json requests.
  • Angular DevTools browser extension helps confirm that the shell and a remote share one Angular runtime (you should see one application root, not two).

Only needed for the deployment page:

  • An Azure subscription with permission to create Static Web Apps or storage accounts.
  • Azure CLI, signed in with az login, if you want to read deployment tokens with az staticwebapp secrets list.
  • A GitHub (or Azure DevOps) repository per deployable app, or one monorepo with one workflow per app.

When everything is in place, this check from an empty directory succeeds without warnings about unsupported versions:

Terminal window
node --version # v22.22.3+, v24.15.0+ or v26.x
npx @angular/cli@22 version
npm view @angular-architects/native-federation version # 22.2.5 at the time of writing
  • The CLI refuses to run and reports an unsupported Node.js version. The @angular/cli 22.2.7 package declares engines.node as ^22.22.3 || ^24.15.0 || >=26.0.0, so early 22.x and 24.x releases are rejected; upgrade within the line, then reinstall node_modules. The CLI’s check is wider than what Angular supports: angular.dev lists ^22.22.3 || ^24.15.0 || ^26.0.0, so a Node.js 27 that the CLI accepts is still untested by the Angular team.
  • npm install reports ERESOLVE with @angular/build as the conflicting peer. The Native Federation adapter’s minor does not match your Angular minor. Install the adapter release that matches (npm view @angular-architects/native-federation versions lists them) or run ng update @angular-architects/native-federation after updating Angular.
  • Instructions for an Angular 22 project install the old webpack builder named above, or use @angular-devkit/build-angular:browser. They target Angular 21 or earlier. Follow Webpack Module Federation for the current builder.
  • Instructions say npm i @angular-architects/native-federation-v4. That bridge package is for Angular 20 and 21 only. On Angular 22 the main package already contains Native Federation v4.
  • Corporate proxy blocks npx. Configure npm’s proxy and https-proxy settings or use your organization’s registry mirror; do not disable TLS verification.

Create the workspace and the two applications in Project setup.