Skip to content

Commit d71818c

Browse files
committed
fix(@angular/cli): explain the latest version fallback when ng add finds 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.
1 parent ad283a6 commit d71818c

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • packages/angular/cli/src/commands/add

‎packages/angular/cli/src/commands/add/cli.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -422,7 +422,7 @@ export default class AddCommandModule
422422
}
423423

424424
if (!found) {
425-
let message = `Unable to find compatible package.`;
425+
let message = `Unable to find compatible package. Using 'latest' tag.`;
426426
if (rejectionReasons.length > 0) {
427427
message +=
428428
'\nThis is often because of incompatible peer dependencies.\n' +

0 commit comments

Comments
 (0)