dependency-compatibility-checker

Resolve peer dependency conflicts by analyzing package.json to identify overlapping version constraints across direct and transitive dependencies. The tool calculates a safe resolution path and outputs an exact resolutions block or npm install command to fix the dependency tree.

Use --legacy-peer-deps when exact version overrides or resolutions blocks cannot satisfy conflicting peer dependency constraints. The tool provides specific guidance on when this flag is necessary versus when a precise version resolution is achievable.

Yes, you can check PHP dependency constraints by parsing composer.json to collect direct and transitive dependencies. It identifies overlapping version requirements and generates a composer update command or resolution path to prevent broken builds.

Transitive dependencies cause peer dependency conflicts when their required version ranges overlap and contradict each other within package.json. The tool detects these peer-hell scenarios by validating all constraint combinations before they break the build.

Yes, dependency compatibility checking verifies runtime compatibility by checking your current Node, Ruby, or PHP tooling versions against the resolved dependency constraints to ensure full environment compatibility.

The best way to prevent peer dependency conflicts is validating version constraints across direct and transitive dependencies before installation. It analyzes package.json or composer.json, identifies overlapping requirements, and proposes the lowest common denominator that satisfies all constraints.