[Yarn3] Installing temporary version of @angular/cli fails
- Lenguaje dominante
- TypeScript
- Estrellas
- 27k
- Forks
- 11.8k
- Merge medio
- 14 h 23 min
- PR fusionados (30 d)
- 162
Descripción
### 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_
Guía de contribución
Línea de trabajo
Comienza con el comando `update` de Angular CLI y reproduce una actualización de Angular 16 a 17 usando Yarn 3 o 4; después, compara la misma actualización con npm. Rastrea dónde se instala la versión temporal de CLI y captura los detalles del fallo; la tarea estará completada cuando la actualización basada en Yarn finalice correctamente.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- angular, typescript
- Área
- cli
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100