[Yarn3] Installing temporary version of @angular/cli fails
- 主要语言
- TypeScript
- 星标
- 27k
- 派生
- 11.8k
- 平均合并
- 14 小时 23 分钟
- 30 天内合并 PR
- 162
描述
### Command
update
### Is this a regression?
- [X] Yes, this behavior used to work in the previous version
### The previous version in which this bug was not present was
V16
### Description
This has happened before (https://github.com/angular/angular-cli/issues/19209) and now happens again when trying to upgrade to angular v17.

Tried to install the update with npm to check if yarn is the cause and npm goes through successfully.

### Minimal Reproduction
Try to upgrade angular 16 to 17 using yarn v3 (current specific version we're using is `v3.6.4`, but I tried to upgrade yarn to `v4.0.2` and it's the same behavior).
Global angular/cli is v17, local is v16 (obviously).
### Exception or Error
_No response_
### Your Environment
```text
Angular CLI: 16.1.6
Node: 18.14.0
Package Manager: yarn 4.0.2
OS: win32 x64
Angular: 16.1.7
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router
Package Version
---------------------------------------------------------
@angular-devkit/architect 0.1601.6
@angular-devkit/build-angular 16.1.6
@angular-devkit/core 16.1.6
@angular-devkit/schematics 16.1.6
@angular/cdk 16.1.6
@angular/cli 16.1.6
@angular/material 16.1.6
@schematics/angular 16.1.6
rxjs 7.8.1
typescript 5.2.2
zone.js 0.14.2
```
### Anything else relevant?
_No response_
贡献指南
调研方向
从 Angular CLI 的 `update` 命令开始,使用 Yarn 3 或 4 重现 Angular 16 到 17 的升级,然后使用 npm 对同一升级进行比较。跟踪临时 CLI 版本的安装位置,并记录失败的详细信息;基于 Yarn 的升级成功完成即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- angular, typescript
- 领域
- cli
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100