Skip to content

feat(hatchet)!: modernize the Effect v4 API #70

Description

@kattsushi

Pre-flight checks

  • I searched existing issues and found no duplicate.
  • I understand implementation requires maintainer approval.

Problem

@effectify/hatchet exposes an alpha workflow-centric API that does not provide the intended Effect v4 task-first model, typed boundaries, scoped resources, or deterministic in-memory execution.

Proposed solution

Modernize the package through a feature-branch chain:

  1. Introduce the typed task core and deterministic direct execution.
  2. Add the verified live Hatchet SDK boundary and scoped worker lifecycle.
  3. Add scheduling, cron, cancellation, and complete consumer migration.

Acceptance boundaries

  • Preserve Effect v4 conventions and typed error/cause channels.
  • Keep live SDK adaptation behind the package boundary.
  • Verify every slice independently with Nx targets and bounded review.
  • Remove the legacy workflow/effectifier surface as a deliberate breaking change.

Delivery

Tracker branch: feat/hatchet-v4-modernization

PR 1 branch: feat/hatchet-v4-core

Metadata

Metadata

Assignees

No one assigned

    Labels

    status:approvedApproved for implementation / PR linkage

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions