Repository navigation
fix(@angular/cli): explain the latest version fallback when ng add finds no compatible version - #34615
fix(@angular/cli): explain the latest version fallback when ng add finds no compatible version#34615MeAkib wants to merge 1 commit into
Conversation
…nds no compatible version When no version of the package satisfies the peer dependencies of the project, `ng add` reports `Unable to find compatible package.` and then continues to install the version of the `latest` tag. The explanation that the `latest` tag is used was dropped when the command was migrated to the new package manager abstraction, so the installation that follows the message is unexpected. Restore the `Using 'latest' tag.` explanation.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the fallback warning message in packages/angular/cli/src/commands/add/cli.ts when a compatible package is not found, explicitly stating that the 'latest' tag will be used. There are no review comments, and I have no additional feedback to provide.
|
Closing this PR as the added text does not reflect the behavior. When no compatible package version is found, the CLI does not fall back to the |
When no version of the package satisfies the peer dependencies of the project,
ng addreportsUnable to find compatible package.and then continues to install the version of thelatesttag. The explanation that thelatesttag is used was dropped when the command was migrated to the new package manager abstraction, so the installation that follows the message is unexpected.Restore the
Using 'latest' tag.explanation.