Contribution

• I'd be willing to implement this feature (contributing guide)

Describe the user story

In pnpm v11, pnpm install no longer displays the details of peer issues, even when strictPeerDependencies is true. This change was added in #11133.

Describe the solution you'd like

I would really appreciate it if this feature could be added back, so that I don't have to run pnpm peers check separately when pnpm install fails.

This would also be beneficial for the Renovate bot log when the installation fails. It would allow me to see immediately why the installation failed without needing to check out the branch locally and run pnpm peers check myself.

For instance, this comment was created by the Renovate bot.

With pnpm v10, the comment looked like this:

⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

website
└─┬ astro 6.1.9
  └─┬ tsconfck 3.1.6
    └── ✕ unmet peer typescript@^5.0.0: found 6.0.3
hint: To disable failing on peer dependency issues, add the following to pnpm-workspace.yaml in your project root:

  strictPeerDependencies: false

With pnpm v11, the comment is:

⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

hint: Run "pnpm peers check" to list the peer dependency issues.
hint: To disable failing on peer dependency issues, add the following to pnpm-workspace.yaml in your project root:

  strictPeerDependencies: false

Describe the drawbacks of your solution

No response

Describe alternatives you've considered

No response