Dependency Conflict Resolution

• Classification: Identify overlapping vs. non-overlapping version requirements.
• Matrix: Map Package A | Package B | Shared Dep | Compatibility.
• Strategy: Use Alignment (Up/Downgrade), Overrides (resolutions), Isolation (Workspaces), or Replacement.
• Fix: Provide commands to regenerate lock files (e.g., rm package-lock.json && npm install).
• Prevention: Recommend major version pinning, CI audits, and automation (Renovate).
• Fallback: If no file, identify conflicting packages and provide tree inspection commands.

Edge Cases

Conflict Workflow

flowchart TD
    A([Start]) --> B[Parse inputs]
    B --> C{Package file?}
    C -- No --> D[Provide inspection command & strategies]
    C -- Yes --> F[Identify Conflict]
    F --> G[Build Compatibility Matrix]
    G --> H{Strategy?}
    H -- Alignment --> I[Upgrade/downgrade]
    H -- Override --> J[Use overrides/resolutions]
    H -- Isolation --> K[Separate workspace]
    H -- Alternative --> L[Replace package]
    I & J & K & L --> M{Platform specific?}
    M -- Yes --> N[Conditional deps]
    M -- No --> O[Provide fix commands]
    N --> O
    O --> P[Add Prevention]
    P --> Q([Output: Report])
    D --> R([Output: Limited diagnosis — inspect tree & retry with package file])

Examples

• Input Example
• Output Example

Quality Gate

• Overlapping range correctly identified.
• Resolution strategy justified.
• Fix commands provided for specific manager.
• Transitive deps mapped.
• Matrix is clear.

MCP Dependencies

• @upstash/context7-mcp: Library documentation and examples.
• @modelcontextprotocol/server-sequential-thinking: Complex reasoning.

Changelog