What problem does it solve?
You need to use Effect services in an environment where Effect does not own the process lifecycle, such as Hono/Express handlers or serverless functions, without manually re-implementing runtime and lifecycle concerns.
Core Features & Use Cases
- Bridge Effect to External Frameworks: Run Effects from non-Effect code paths using ManagedRuntime in HTTP handlers, serverless functions, or embedded contexts.
- Correct Lifecycle & Resource Safety: Dispose the runtime to release resources acquired during layer construction (DB pools, clients, file handles).
- Deterministic Execution Options: Use runPromise for async handlers, runSync for known-sync effects, and runFork/runCallback for alternative execution styles.
- Integration Ready: Includes guidance and examples for Hono, Express, AWS Lambda, and Cloudflare Workers, plus key contrasts vs Layer.launch and runMain.
Quick Start
Use the effect-managed-runtime skill to run your Effect services inside a Hono or Express route by constructing a ManagedRuntime from your app layer and calling runtime.runPromise within the handler.