Skip to content

fix: use effect 4.x matching opencode #270

Merged
mrsimpson merged 1 commit intomainfrom
fix-ask-for-permissions
Apr 23, 2026
Merged

fix: use effect 4.x matching opencode #270
mrsimpson merged 1 commit intomainfrom
fix-ask-for-permissions

Conversation

@mrsimpson
Copy link
Copy Markdown
Collaborator

to fix cross-module Effect incompatibility

Effect 3.x uses unique Symbol for TypeId; Effect 4.x uses the plain string '~effect/Effect'. Running Effect.runPromise from a bundled 3.x instance on a 4.x Effect object fails with 'Not a valid effect: {}' because isEffect() uses a Symbol lookup that cannot find the string-keyed property.

Pinning effect to 4.0.0-beta.48 (matching opencode) and adding a local tsconfig.json with moduleResolution:bundler so DTS generation resolves the package exports correctly.

…mpatibility

Effect 3.x uses unique Symbol for TypeId; Effect 4.x uses the plain string
'~effect/Effect'. Running Effect.runPromise from a bundled 3.x instance on
a 4.x Effect object fails with 'Not a valid effect: {}' because isEffect()
uses a Symbol lookup that cannot find the string-keyed property.

Pinning effect to 4.0.0-beta.48 (matching opencode) and adding a local
tsconfig.json with moduleResolution:bundler so DTS generation resolves the
package exports correctly.
@mrsimpson mrsimpson merged commit 02ce1d0 into main Apr 23, 2026
3 checks passed
@mrsimpson mrsimpson deleted the fix-ask-for-permissions branch April 23, 2026 05:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant