Handling Unmet Peer Dependencies in Effect Typescript Library

How do you usually deal with this?

apps/blog
├─┬ @effect/cluster 0.30.11
│ └── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3
├─┬ @effect/rpc 0.56.9
│ └── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3
├─┬ @effect/sql 0.33.21
│ └── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3
├─┬ @effect/experimental 0.44.21
│ └── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3
├─┬ @effect/cli 0.59.21
│ └── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3
└─┬ @effect/platform-node 0.77.11
  ├── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3
  └─┬ @effect/platform-node-shared 0.31.11
    └── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3

libs/cli
├─┬ @effect/cluster 0.30.11
│ └── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3
├─┬ @effect/sql 0.33.21
│ └── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3
├─┬ @effect/cli 0.59.21
│ └── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3
└─┬ @effect/platform-node 0.77.11
  ├── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3
  └─┬ @effect/platform-node-shared 0.31.11
    └── ✕ unmet peer @effect/platform@^0.80.21: found 0.82.3
Was this page helpful?