Effect-TS /effect
Build production-ready applications in TypeScript
★ 17,575⑂ 912👁 36⑃ 8,304● 2,301▤ 11,195
+9
Daily
+106
Weekly
+327
Monthly
17,575
stars
912
forks
36
watchers
8,304
prs
2,301
issues
11,195
releases
README
Effect Effect is a library for building robust, maintainable, type-safe, and production grade applications in TypeScript. It helps you handle the hard problems at scale: typed errors, dependency injection, structured concurrency, scheduling, tracing, and unified schema validation. Effect 4.x is a long-term support (LTS) release. If you are upgrading from Effect 3.x, follow the migration guide. Installation sh npm install effect Requirements - TypeScript 5.9 or newer. TypeScript 7 is recommended for the best performance and compatibility with Effect's TypeScript tooling. - Node.js 22.19 or newer is the general minimum for running Effect on Node.js. - Strict type-checking: the strict flag must be enabled in your tsconfig.json. Links - Website: documentation, guides, and news - Discord: ask questions, share what you're building, and talk to the core team - Community: meetups and events, or bring Effect to your own - Issues: bug reports and feature requests - Jobs: companies hiring Effect developers - Follow us on X, Bluesky, and LinkedIn Let's talk Whether your team is considering Effect, rolling it out, or already running it in production, we'd love to hear from you: what you're building, what works, and what you need from Effect next. - Talk to the maintainers. Introduce your team on Discord or email [email protected]. We're happy to connect privately on Slack or Discord for feedback and help with adoption. - Production support. We're exploring how to better support teams running Effect in production. If your organization has specific support needs, let's discuss them. - Adoption help. Our adoption partners offer implementation, consulting, team extension, training, and commercial support. Feedback from teams using and evaluating Effect directly shapes what we stabilize and build next. Long-term support Teams depend on Effect for systems they expect to run for years. Effect 4.x is a long-term support (LTS) release with the following guarantees: - At least three years of support, including bug and security fixes. - Bug fixes for one year after the next major version is released. - Security fixes for two years after the next major version is released. Stable APIs reserve breaking changes for major releases. APIs marked unstable may change in minor releases, and experimental APIs may change in patch releases. Effect v3 The Effect v3 source code is available on the v3 branch, which is also where issues and pull requests meant for Effect v3 should be targeted. To upgrade, see the migration guide. Packages This monorepo contains the core effect package alongside integration packages that extend it. All packages listed below are released together with synchronized versions. | Package | Description | API Reference | | ------------------------------------------------
Top issues
#6353McpServer: no first-class support for MCP Apps (SEP-1865 / interactive UI resources)9 comments · 2026-05-17#8123Comparing and fingerprinting persisted schemas4 comments · 2026-09-07#6752McpServer.layerHttp: support a stateless Streamable HTTP mode for serverless runtimes4 comments · 2026-07-29#9882HttpApiClient: `Redacted` query and header values appear in plain text in client spans3 comments · 2026-10-24#6834add first-class support for tasks extension3 comments · 2026-08-01#10399effect/ai: support the MCP Apps extension (`io.modelcontextprotocol/ui`)2 comments · 2026-11-05#10394Support `format: "password"` as `Redacted` in JSON Schema import/export and the OpenAPI generator2 comments · 2026-11-05#10383Versioned schemas with version negotiation in HttpApi, Rpc and cluster2 comments · 2026-11-04
Latest release
@effect/[email protected] @effect/[email protected] 2026-11-11Patch Changes - 10521 edb2eaa Thanks @gcanti! - Add experimental closeObjects, fix JSON Schema composition and examples, and regenerate a smaller OpenRouter client with a boolean workspace-deletion confirmation flag. Breaking changes The generated OpenRouter schemas follow the current upstream specification. Some intermediate schema exports are removed; derive their types from the corresponding request or response schema instead. Hand-built generation statistics must now include workspace_id, and activity entries must include cached_tokens. Tool parameter and structured-output sche