CodeVetter · Repo Unpack · System map
effect-ts/effect
The repository is a pnpm workspace organized around the core effect package and technology-specific integrations. Public entrypoints expose TypeScript source during workspace development and compiled JavaScript when published. Context, Layer, fibers, and scopes provide the shared execution architecture across these packages. Build, verification, generation, and release workflows are repository-level concerns rather than an application deployment stack.
- The core effect manifest declares version 4.0.0, exports src/index.ts and subsystem entrypoints such as effect/http and effect/sql, and redirects published exports to dist while blocking internal paths.
- Context owns typed service maps; Layer<ROut, E, RIn> constructs service contexts with scoped acquisition; ManagedRuntime caches that context and owns separate layer and execution-fiber scopes.
- Platform boundaries are replaceable services: NodeHttpServer adapts Node request, response, and upgrade events, while FetchHttpClient supports Web Fetch environments and an injectable Fetch reference.
- Storage is supplied through implementations rather than one repository-wide database: KeyValueStore provides memory, filesystem, and SQL layers; the Node SQLite layer supplies both SqliteClient and generic SqlClient.
- Separate integrations provide Anthropic, OpenAI, OpenAI-compatible, OpenRouter, and TypeSafe AI backends; React, Solid, and Vue atom bindings; and OpenTelemetry support.
- Root build runs TypeScript project references, recursive package builds, and AI-document copying; package builds compile then Babel-annotate pure calls. Root scripts also expose lint, circular-dependency checks, API diff, and runtime/type performance harnesses.
- Check CI combines static, type, build, bundle, runtime, and documentation jobs; bundle-comment consumes its validated stats artifact, while nightly ai-codegen generates provider updates and conditionally opens a PR.
- Release packaging uses Changesets with a fixed synchronized package group; main releases can publish and dispatch website deployment, snapshots publish PR packages after fork gating, and release-queue manages eligible next-release branches.