[ENHANCEMENT] Please update this warning to be more clear.

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: @com.txdot.cris/ui@0.0.0
npm ERR! Found: @angular/common@16.2.12
npm ERR! node_modules/@angular/common
npm ERR! @angular/common@"^16.2.12" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/common@"^17.0.3" from angular-google-tag-manager@1.9.0
npm ERR! node_modules/angular-google-tag-manager
npm ERR! angular-google-tag-manager@"^1.8.0" from the root project

This error always leads our developers down the wrong path trying to troubleshoot npm. They usually start by pointing at npm or Nexus. Why? Because it says "Could not resolve dependency:" they immediately think it can't find the dependency in Nexus or the npm repos. What it really means is that there is a dependency conflict because angular-google-tag-manager 1.9.0 depends on Angular 17, and we are using Angular 16. If it said, "Could not resolve a peer dependency conflict:" it would help a lot.

Expected Behavior

N/A

Steps To Reproduce

N/A

Environment

N/A

No file, test, or entry point is named. Search the CLI for the ERESOLVE output and trace the warning-generation path, then find its message tests. Done means the warning explicitly identifies the peer dependency conflict and the tests cover the revised wording.