Skip to content

Update Guide doesn't mention that further packages should be updated at the same time as @angular/core and @angular/cli #65692

@karcherm

Description

@karcherm

Describe the problem that you experienced

See angular-eslint/angular-eslint#2807

I upgraded a project using angular-eslint trying to follow the Update Guide, and encountered a failing migration when executing ng update angular-eslint@20. I think I understand the technical background, and I understand that this issue is avoided by upgrading angular-eslint at the same time as @angular/core and @angular/cli. This is the upgrade procedure recommended by the author of angular-eslint.

Enter the URL of the topic with the problem

https://angular.dev/update-guide?v=19.0-20.0&l=1

Describe what you were looking for in the documentation

I was looking for a guide that explains how to migrate a real-world project (which should include some kind of code quality assurance) from Angular 19 to Angular 20

Describe the actions that led you to experience the problem

I followed the instructions as written, and then started to upgrade the "non-vital" components (and I assumed angular-eslint to be "non-vital") only after the recommended steps in the upgrade guide were complete.

Describe what you want to experience that would fix the problem

The step "In the application's project directory, run ng update @angular/core@20 @angular/cli@20 to update your application to Angular v20." could be extended by a hint that upgrading further angular-specific packages (like angular-oauth2-oidc or angular-eslint) are best upgraded in the same command line.

Add a screenshot if that helps illustrate the problem

No response

If this problem caused an exception or error, please paste it here

As shown in the linked bug report to `angular-eslint`:


STEP 11/13: RUN npx ng update angular-eslint@20 || true

> [email protected] ng
> ng update angular-eslint@20

Using package manager: npm
Collecting installed dependencies...
Found 24 dependencies.
Fetching dependency metadata from registry...
    Updating package.json with dependency angular-eslint @ "20.7.0" (was "19.8.1")...
UPDATE package.json (1123 bytes)
❯ Cleaning node modules directory
✔ Cleaning node modules directory
❯ Installing packages
✔ Installing packages
** Executing migrations of package 'angular-eslint' **

❯ Updates @angular-eslint to v20.
UPDATE package.json (1123 bytes)
✖ Migration failed: Cannot find module '../package-manager/executor'
Require stack:
- /demo/node_modules/@angular/cli/node_modules/@angular-devkit/schematics/tasks/node/index.js
- /demo/node_modules/@angular/cli/node_modules/@angular-devkit/schematics/tools/workflow/node-workflow.js
- /demo/node_modules/@angular/cli/node_modules/@angular-devkit/schematics/tools/index.js
- /demo/node_modules/@angular/cli/src/commands/update/cli.js
- /demo/node_modules/@angular/cli/src/commands/command-config.js
- /demo/node_modules/@angular/cli/src/command-builder/command-runner.js
- /demo/node_modules/@angular/cli/lib/cli/index.js
- /demo/node_modules/@angular/cli/lib/init.js
  See "/tmp/ng-E8vcjp/angular-errors.log" for further details.

If the problem is browser-specific, please specify the device, OS, browser, and version


Provide any additional information here in as much as detail as you can


Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions