What problem does it solve?
Prevents broken builds caused by mismatched or conflicting dependencies by enforcing a Pixi-first installation and command workflow across npm, yarn, and cargo ecosystems.
Core Features & Use Cases
- Pixi-first dependency management: Uses Pixi as the central manager to provide consistent, reproducible environments via lock files.
- Command conversion rules: Translates legacy npm/yarn/cargo workflows into equivalent
pixi run ... patterns (including dlx for one-off executions).
- Conflict detection and resolution guidance: Helps diagnose common coupling issues like PyTorch/torchvision/torchaudio alignment, Python version constraints, CUDA mismatches, and channel conflicts; supports targeted environment selection (e.g., js/cuda/aios/llmops/docs/ros2).
Example: You need to add a new Node and Rust dependency for a robotics project and avoid environment drift that causes “it works on my machine” failures after reloads.
Quick Start
Convert your installation and build commands to Pixi-run equivalents and verify compatibility by checking the relevant environment-specific dependency and conflict patterns, starting with the Node scope via pnpm.