Problem
dfx 0.127.0 declares peer dependencies effect ^3.19 and @effect/platform ^0.93. While ^3.19 technically accepts Effect 3.21, the transitive @effect/* dependencies (@effect/cluster, @effect/rpc, @effect/sql, etc.) are pinned to older versions that pull in their own effect copies. This causes duplicate effect versions in pnpm lockfiles, which leads to runtime issues and bloated node_modules.
The broader Effect 3.x ecosystem has moved to effect 3.21.0 / @effect/platform 0.96.0, so a dfx release with updated @effect/* deps would help downstream consumers avoid these version conflicts.
Request
A 0.128+ release targeting the current Effect 3.21 ecosystem would be much appreciated. I understand the 1.x line targets the Effect 4.0 beta, so this would serve as an interim solution for projects that are still on Effect 3.x but want to stay current within that major.
Created on behalf of @schickling by an AI coding agent.
Problem
dfx 0.127.0 declares peer dependencies
effect ^3.19and@effect/platform ^0.93. While^3.19technically accepts Effect 3.21, the transitive@effect/*dependencies (@effect/cluster,@effect/rpc,@effect/sql, etc.) are pinned to older versions that pull in their own effect copies. This causes duplicateeffectversions in pnpm lockfiles, which leads to runtime issues and bloatednode_modules.The broader Effect 3.x ecosystem has moved to
effect 3.21.0/@effect/platform 0.96.0, so a dfx release with updated@effect/*deps would help downstream consumers avoid these version conflicts.Request
A
0.128+release targeting the current Effect 3.21 ecosystem would be much appreciated. I understand the 1.x line targets the Effect 4.0 beta, so this would serve as an interim solution for projects that are still on Effect 3.x but want to stay current within that major.Created on behalf of @schickling by an AI coding agent.