8000 `ng update` throws `Unable to resolve migrations for package (@angular/cli)` for v20 with pnpm · Issue #30328 · angular/angular-cli · GitHub
[go: up one dir, main page]
Skip to content

ng update throws Unable to resolve migrations for package (@angular/cli) for v20 with pnpm #30328

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
1 task done
cexbrayat opened this issue May 16, 2025 · 2 comments
Closed
1 task done

ng update throws Unable to resolve migrations for package (@angular/cli) for v20 with pnpm #30328

cexbrayat opened this issue May 16, 2025 · 2 comments

Comments

@cexbrayat
Copy link
Member

Command

update

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

When trying to run the migration to v20 using ng update in a CLI project in v19 with pnpm, the ng update command throws.

Minimal Reproduction

Create a new v19 project

npx @angular/cli new migration-v20 --defaults --no-routing
cd migration-v20
pnpm i

Edit angular.json to add:

"cli": {
  "packageManager": "pnpm"
},

Run the migration to CLI v20 (rc.2 when writing this issue):

ng update @angular/cli@next --force

Exception or Error

Using package manager: pnpm
Collecting installed dependencies...
Found 21 dependencies.
Fetching dependency metadata from registry...
    Updating package.json with dependency @angular-devkit/build-angular @ "20.0.0-rc.2" (was "19.2.12")...
    Updating package.json with dependency @angular/cli @ "20.0.0-rc.2" (was "19.2.12")...
    Updating package.json with dependency @angular/compiler-cli @ "20.0.0-rc.1" (was "19.2.11")...
    Updating package.json with dependency typescript @ "5.8.3" (was "5.7.3")...
    Updating package.json with dependency @angular/common @ "20.0.0-rc.1" (was "19.2.11")...
    Updating package.json with dependency @angular/compiler @ "20.0.0-rc.1" (was "19.2.11")...
    Updating package.json with dependency @angular/core @ "20.0.0-rc.1" (was "19.2.11")...
    Updating package.json with dependency @angular/forms @ "20.0.0-rc.1" (was "19.2.11")...
    Updating package.json with dependency @angular/platform-browser @ "20.0.0-rc.1" (was "19.2.11")...
    Updating package.json with dependency @angular/platform-browser-dynamic @ "20.0.0-rc.1" (was "19.2.11")...
    Updating package.json with dependency @angular/router @ "20.0.0-rc.1" (was "19.2.11")...
UPDATE package.json (1056 bytes)
✔ Cleaning node modules directory
✔ Installing packages
Unable to resolve migrations for package (@angular/cli).  [ENOENT: no such file or directory, lstat '/Users/cedric/Code/temp/migration-v20/node_modules/.pnpm/@angular+cli@19.2.12_@types+node@22.15.18_chokidar@4.0.3/node_modules/@angular/cli/package.json']

Your Environment

Angular CLI: 20.0.0-rc.2
Node: 22.14.0
Package Manager: pnpm 10.8.1
OS: darwin arm64

Angular: 20.0.0-rc.1
... common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.2000.0-rc.2
@angular-devkit/build-angular   20.0.0-rc.2
@angular-devkit/core            20.0.0-rc.2
@angular-devkit/schematics      20.0.0-rc.2
@angular/cli                    20.0.0-rc.2
@schematics/angular             20.0.0-rc.2
rxjs                            7.8.2
typescript                      5.8.3
zone.js                         0.15.0

Anything else relevant?

No response
@clydin
Copy link
Member
clydin commented May 16, 2025

Can you try with ng update @angular/cli --next instead?

@cexbrayat
Copy link
Member Author

That works indeed 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cexbrayat @clydin
0