Skip to content

Migration fails for Ng13 -> Ng14 (Incompatibility with yarn v3 with --force flag) #23495

Closed

Description

@Lonli-Lokli

🐞 Bug report

Command (mark with an x)

  • new
  • build
  • serve
  • test
  • e2e
  • generate
  • add
  • update
  • lint
  • extract-i18n
  • run
  • config
  • help
  • version
  • doc

Is this a regression?

No

Description

In the case when package manager is Yarn3 & there are Incompatible peer dependencies, migration fails for Ng13 -> Ng14
Looks like #22048 has not been fully fixed.

🔬 Minimal Reproduction

  1. Clone and switch to initial branch
    https://github.com/Lonli-Lokli/angular-cli-diff/tree/initial

  2. Run npx ng update @angular/core@14 @angular/cli@14 --force

🔥 Exception or Error


> Update Angular packages 'dependencies' and 'devDependencies' version prefix to '^' instead of '~'.
UPDATE package.json (1484 bytes)
✖ Package install failed, see above.
× Migration failed. See above for further details.

🌍 Your Environment


Angular CLI: 13.3.8
Node: 14.18.2
Package Manager: yarn 3.2.1
OS: win32 x64

Angular: 13.3.11
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1303.8
@angular-devkit/build-angular   13.3.8
@angular-devkit/core            13.3.8
@angular-devkit/schematics      13.3.8
@angular/cli                    13.3.8
@schematics/angular             13.3.8
rxjs                            7.5.5
typescript                      4.6.4

Activity

  1. self-assigned this
    on Jul 4, 2022
  2. added 2 commits that reference this issue on Jul 4, 2022
    61a3d34
    1527714
  3. added 2 commits that reference this issue on Jul 6, 2022
    98a6aad
    cbccfd4
  4. angular-automatic-lock-bot commented on Aug 6, 2022

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  5. locked and limited conversation to collaborators on Aug 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions