ERESOLVE unable to resolve dependency tree: peer dependency conflict reporting

ERESOLVE unable to resolve dependency tree

When pnpm encounters a peer dependency conflict during resolution, it emits the error ERESOLVE unable to resolve dependency tree. This message signals that the resolver cannot satisfy the declared peer constraints across the dependency graph.

The current documentation does not specify a consistent policy for handling such conflicts. Some releases fail immediately, others provide a warning, and a few attempt automatic resolution. This ambiguity complicates reproducible builds, especially in monorepo environments where multiple packages declare overlapping peer dependencies.

To design reliable CI pipelines, we need to understand the intended behavior and how it evolves across pnpm versions. The following questions remain unanswered:

• What is pnpm’s official policy for peer dependency conflicts in the latest stable release?
• Do newer releases (v8.x and v9.x) introduce deterministic conflict‑resolution strategies, or does the behavior remain version‑dependent?
• How can we programmatically detect and react to these conflicts to ensure consistent installation outcomes?