Skip to content

Widen the exact effect@4.0.0-beta.59 peer pin (and rebuild against a current Effect 4 RC) #1923

Description

@methodacting

Every published version of @executor-js/sdk and @executor-js/plugin-openapi (1.6.3 through 2.0.0) declares an exact peer pin:

"effect": "4.0.0-beta.59"

(same for @effect/atom-react and @effect/platform-node). Because these are peers, consumers supply their own Effect — so anyone tracking the Effect 4 line past beta.59 is out of contract immediately, and there is no version to upgrade to.

It currently also breaks at runtime, not just at resolution: the published dist calls Schema.TaggedErrorClass(, which Effect renamed to Schema.TaggedError in 4.0.0-rc.112, so the SDK throws at module load under current RCs. (Later betas happened to still carry the old name, which masked the pin violation.)

Would you consider widening the peer to a range (e.g. >=4.0.0-beta.105 || >=4.0.0, the shape drizzle-orm 1.0.0-rc.5 uses) and rebuilding against a current RC? Happy to send a PR for the peer-range change if that helps. For now we're carrying a two-line dist patch (TaggedErrorClass(TaggedError() via pnpm patchedDependencies, which works but shouldn't need to exist.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions