Skip to content

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

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.

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

Closed
1 of 15 tasks
Lonli-Lokli opened this issue Jul 4, 2022 · 1 comment · Fixed by #23500
Closed
1 of 15 tasks
Assignees
Labels

Comments

@Lonli-Lokli
Copy link

🐞 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

@alan-agius4 alan-agius4 self-assigned this Jul 4, 2022
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this issue Jul 4, 2022
…tion with npm 7+

In some cases previously we passed the `force` option to yarn which which lead to an installation failure.

Closes angular#23495
alan-agius4 added a commit to alan-agius4/angular-cli that referenced this issue Jul 4, 2022
…tion with npm 7+

In some cases previously we passed the `force` option to yarn which which lead to an installation failure.

Closes angular#23495
alan-agius4 added a commit that referenced this issue Jul 6, 2022
…tion with npm 7+

In some cases previously we passed the `force` option to yarn which which lead to an installation failure.

Closes #23495

(cherry picked from commit cbccfd4)
alan-agius4 added a commit that referenced this issue Jul 6, 2022
…tion with npm 7+

In some cases previously we passed the `force` option to yarn which which lead to an installation failure.

Closes #23495
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Aug 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
2 participants