Managing Peer Dependencies with pnpm and Versioning Challenges
Is there a good way to keep track of all the peer deps? LIke
I typically use pnpm catalogs, but it can be tricky to manage the versioning.
e2e/mock-api-v2
├─┬ vitest 3.2.4
│ └── ✕ unmet peer @vitest/ui@3.2.4: found 3.0.4
└─┬ @effect/platform-node 0.88.11
├── ✕ unmet peer @effect/rpc@^0.64.8: found 0.64.1
├── ✕ unmet peer @effect/sql@^0.40.8: found 0.40.0
├── ✕ unmet peer @effect/cluster@^0.41.11: found 0.41.2
└─┬ @effect/platform-node-shared 0.42.18
├── ✕ unmet peer @effect/rpc@^0.64.14: found 0.64.1
├── ✕ unmet peer @effect/sql@^0.40.14: found 0.40.0
└── ✕ unmet peer @effect/cluster@^0.41.18: found 0.41.2
packages/davinci-client
└─┬ vitest 3.0.5
└── ✕ unmet peer @vitest/ui@3.0.5: found 3.0.4
tools/user-scripts
├─┬ vitest 3.2.4
│ └── ✕ unmet peer @vitest/ui@3.2.4: found 3.0.4
└─┬ @effect/platform-node 0.88.11
├── ✕ unmet peer @effect/rpc@^0.64.8: found 0.64.1
├── ✕ unmet peer @effect/sql@^0.40.8: found 0.40.0
├── ✕ unmet peer @effect/cluster@^0.41.11: found 0.41.2
└─┬ @effect/platform-node-shared 0.42.18
├── ✕ unmet peer @effect/rpc@^0.64.14: found 0.64.1
├── ✕ unmet peer @effect/sql@^0.40.14: found 0.40.0
└── ✕ unmet peer @effect/cluster@^0.41.18: found 0.41.2e2e/mock-api-v2
├─┬ vitest 3.2.4
│ └── ✕ unmet peer @vitest/ui@3.2.4: found 3.0.4
└─┬ @effect/platform-node 0.88.11
├── ✕ unmet peer @effect/rpc@^0.64.8: found 0.64.1
├── ✕ unmet peer @effect/sql@^0.40.8: found 0.40.0
├── ✕ unmet peer @effect/cluster@^0.41.11: found 0.41.2
└─┬ @effect/platform-node-shared 0.42.18
├── ✕ unmet peer @effect/rpc@^0.64.14: found 0.64.1
├── ✕ unmet peer @effect/sql@^0.40.14: found 0.40.0
└── ✕ unmet peer @effect/cluster@^0.41.18: found 0.41.2
packages/davinci-client
└─┬ vitest 3.0.5
└── ✕ unmet peer @vitest/ui@3.0.5: found 3.0.4
tools/user-scripts
├─┬ vitest 3.2.4
│ └── ✕ unmet peer @vitest/ui@3.2.4: found 3.0.4
└─┬ @effect/platform-node 0.88.11
├── ✕ unmet peer @effect/rpc@^0.64.8: found 0.64.1
├── ✕ unmet peer @effect/sql@^0.40.8: found 0.40.0
├── ✕ unmet peer @effect/cluster@^0.41.11: found 0.41.2
└─┬ @effect/platform-node-shared 0.42.18
├── ✕ unmet peer @effect/rpc@^0.64.14: found 0.64.1
├── ✕ unmet peer @effect/sql@^0.40.14: found 0.40.0
└── ✕ unmet peer @effect/cluster@^0.41.18: found 0.41.2I typically use pnpm catalogs, but it can be tricky to manage the versioning.
