Failed update prevents further updates
- Dominant language
- TypeScript
- Stars
- 27k
- Forks
- 11.8k
- Avg merge
- 14h 23m
- Merged PRs (30d)
- 162
Description
This issue impacts 9.0.0-rc.0 and happened while updating https://github.com/vmware/clarity.
After a failed update such as described in https://github.com/angular/angular-cli/issues/16019, the project will have already been updated to the latest versions.
Attempting to update again will inform the user that everything is up to date.
```
kamik@RED-X1C6 MINGW64 /d/sandbox/clarity (update-9)
$ ng update @angular/cli @angular/core --next --force
Using package manager: 'npm'
Collecting installed dependencies...
Found 109 dependencies.
Fetching dependency metadata from registry...
Package '@angular/cli' is already up to date.
Package '@angular/core' is already up to date.
```
This is inaccurate as the update did not actually complete successfully. To redo the update, a user will have to manually undo commits and reinstall packages, and only then will they be able to attempt to update again.
Contributor guide
Research direction
Start with the `ng update @angular/cli @angular/core --next --force` command and reproduce the failed-update sequence described in issue #16019. Trace the update entry point to determine why a failed run is reported as already up to date; done means a user can retry the update without manually undoing commits or reinstalling packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular, typescript
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100