如何在保留Angular 10版本的前提下将Nx 10工作区升级至Nx 12？

Absolutely, this is achievable! Nx lets you upgrade its core workspace version while keeping your Angular 10 setup intact—you just need to manually tweak the migration configuration to lock Angular's version. Here's a detailed, step-by-step breakdown:

Step 1: Generate Nx 12 Migration Configuration #

First, initiate the migration targeting Nx 12 specifically (avoid using latest, which auto-upgrades Angular by default). Run this command in your workspace root:

nx migrate @nrwl/workspace@12

This creates a migrate.json file in your root directory, listing all packages scheduled for upgrade.

Step 2: Lock Angular Versions in Migration Config #

Open the migrate.json file and find all entries starting with @angular/ (e.g., @angular/core, @angular/cli, @angular/common). For each of these packages, replace the proposed upgrade version with your exact current Angular 10 version (pull this from your package.json to ensure consistency).

Note: You can safely upgrade Nx-specific Angular packages like @nrwl/angular to version 12—these are fully compatible with Angular 10 and need to match your Nx core version.

Step 3: Install Updated Dependencies #

Run your package manager's install command to apply the modified configuration. This will upgrade Nx-related packages to 12 while leaving Angular 10 packages untouched:

# For npm users
npm install

# For yarn users
yarn install

Step 4: Run Nx Migration Scripts #

Execute the migration scripts to update your workspace configuration files (like nx.json, angular.json) to Nx 12 standards, without altering Angular-specific code or dependencies:

nx migrate --run-migrations=migrate.json

Step 5: Verify the Upgrade #

Confirm the upgrade worked as expected by checking versions:

# Check Nx version (should show 12.x)
nx --version

# Check Angular version (should still show 10.x)
ng version

Then run your project's build, test, or serve commands to ensure no breaking changes were introduced.

Key Notes #

• Double-check third-party dependencies: Some libraries might have compatibility rules for both Nx 12 and Angular 10. Resolve any dependency conflicts by adjusting package versions in package.json if needed.
• Review migration logs: If any steps fail, logs will flag specific issues—address these manually before re-running the migration scripts.

内容的提问来源于stack exchange，提问作者Magnum23