Generated projects pin effect to rc.108, but a fresh install can resolve a newer @effect/platform-node-shared. Node and Nx E2E builds then fail:
Could not resolve "effect/ByteSize"
@effect/platform-node-shared@4.0.0-rc.117
with effect@4.0.0-rc.108
Define a compatible generated Effect package set and prevent transitive prerelease drift for Bun and Node package managers. Validate real generated projects before changing catalog strings.
Updating all generated packages to rc.115 is not a version-only fix: an exploratory workspace also exposed old calls such as Config.string and AI workflow typing errors. Include the required generated API migration, or deliberately pin a supported older set.
Done when fresh Bun and pnpm installs type-check and build the Node-compatible targets and Nx profile. Keep their E2E coverage. This complements #255's broad catalog/chat validation issue.
Generated projects pin
effectto rc.108, but a fresh install can resolve a newer@effect/platform-node-shared. Node and Nx E2E builds then fail:Define a compatible generated Effect package set and prevent transitive prerelease drift for Bun and Node package managers. Validate real generated projects before changing catalog strings.
Updating all generated packages to rc.115 is not a version-only fix: an exploratory workspace also exposed old calls such as
Config.stringand AI workflow typing errors. Include the required generated API migration, or deliberately pin a supported older set.Done when fresh Bun and pnpm installs type-check and build the Node-compatible targets and Nx profile. Keep their E2E coverage. This complements #255's broad catalog/chat validation issue.