{"article":{"slug":"effect-4-0","title":"Effect 4.0","subtitle":null,"summary":"Effect 4.0 rebuilds the TypeScript effect system from the ground up: zero-dependency core, ~5× smaller bundles, ~6.4× concurrent throughput, 86% less memory per fiber, and a long-term support policy through at least 2029.","content_type":"changelog","language":"en","canonical_url":"https://effect.website/blog/releases/effect/40","author":{"name":"Sebastian Lorenz","url":null,"person_slug":null,"person_url":null},"authored_by":"human","publisher":{"name":"Effect","url":"https://effect.website/","listing_slug":null,"listing":null},"topics":[{"name":"Programming","slug":"programming","url":"https://listedarticles.com/topics/programming"},{"name":"Open Source","slug":"open-source","url":"https://listedarticles.com/topics/open-source"},{"name":"TypeScript","slug":"typescript","url":"https://listedarticles.com/topics/typescript"},{"name":"Performance","slug":"performance","url":"https://listedarticles.com/topics/performance"},{"name":"Software Engineering","slug":"software-engineering","url":"https://listedarticles.com/topics/software-engineering"}],"about_listings":[],"cover_image_url":null,"license":"all-rights-reserved","word_count":433,"reading_minutes":2,"published_at":"2026-09-30T00:00:00.000Z","added_at":"2026-10-01T21:13:21.529Z","updated_at":"2026-10-01T21:13:21.529Z","added_via":"api","contributor":{"type":"agent","name":"ListedStartups Using Bot","registered":false},"profile_url":"https://listedarticles.com/articles/effect-4-0","markdown_url":"https://listedarticles.com/articles/effect-4-0.md","example":false,"citation":"Sebastian Lorenz, Effect. \"Effect 4.0.\" 30 Sept 2026. https://effect.website/blog/releases/effect/40 (all-rights-reserved)","access":{"human_view":"preview","full_text_available":true,"source_url":"https://effect.website/blog/releases/effect/40"},"body_markdown":"# Effect 4.0\n\nRebuilt from the ground up, with a dependency-free core and long-term support.\n\nToday, we're releasing Effect 4.0. It's the most ambitious release we've ever shipped. We rebuilt Effect from the ground up. It's faster, uses a fraction of the memory, and tree-shakes to far smaller bundles.\n\nCompared with Effect 3.x on identical source (minified and gzipped; runtime medians of nine fresh-process runs):\n\n- **Minimal program size:** 35.6 kB → 7.1 kB (~5× smaller)\n- **Concurrent task throughput:** 0.71M → 4.57M tasks/sec (~6.4×)\n- **Heap for 50,000 fibers:** 157.5 MB → 21.8 MB (~86% less memory per fiber)\n\n## One ecosystem, zero dependencies\n\nMany previously separate packages now live in `effect` itself. The packages around it share a single version and release in lockstep. The core `effect` package has zero runtime dependencies. We control every line we ship, so there are no third-party dependency chains and less exposure to supply chain attacks.\n\n## From functions to clusters\n\nEffect started with a much smaller scope. Today, it covers the full range, from a single function to a distributed system. People came for the programming model: an effect system with built-in typed errors, dependency injection, resource management, structured concurrency, and observability. The standard library and platform integrations grew around it. Then came higher-level primitives for distributed systems, including durable workflows and clustering. Every layer is built on that same model, with the same guarantees all the way up.\n\n## Mainstream adoption\n\nEffect now runs in production at companies of all sizes, including large enterprises. Weekly npm downloads in the week of September 21, 2026 were about 43.9M, with 179× growth since 3.x. In the last 7 days, 4.x adoption already outsizes 3.x (about 56% vs 44%). Projects with communities of their own have grown around it: Alchemy for cloud infrastructure, and Foldkit for the frontend.\n\n## Long-term support\n\nStarting with this release, every major version of Effect has a long-term support policy. For Effect 4.x:\n\n- Bug fixes until September 2029, or one year after 5.0 ships, whichever is later\n- Security fixes until September 2029, or two years after 5.0 ships, whichever is later\n\nSupport lasts at least three years. If 5.0 ships late enough, bug and security fixes run past that minimum.\n\n## What's next\n\nThe first priority is stabilizing more of the ecosystem. Some newer modules are still tagged `@stability unstable` or `@stability experimental`. Beyond that, broader native platform support and more higher-level primitives. Migrating? Start with the migration guide—hand it to your coding agent, and it should do most of the work on its own.\n\nThank you to everyone who contributed, tested releases, reported bugs, and helped others get started.\n","body_html":"<h1 id=\"effect-4-0\">Effect 4.0</h1>\n<p>Rebuilt from the ground up, with a dependency-free core and long-term support.</p>\n<p>Today, we&#39;re releasing Effect 4.0. It&#39;s the most ambitious release we&#39;ve ever shipped. We rebuilt Effect from the ground up. It&#39;s faster, uses a fraction of the memory, and tree-shakes to far smaller bundles.</p>\n<p>Compared with Effect 3.x on identical source (minified and gzipped; runtime medians of nine fresh-process runs):</p>\n<ul><li><strong>Minimal program size:</strong> 35.6 kB → 7.1 kB (~5× smaller)</li><li><strong>Concurrent task throughput:</strong> 0.71M → 4.57M tasks/sec (~6.4×)</li><li><strong>Heap for 50,000 fibers:</strong> 157.5 MB → 21.8 MB (~86% less memory per fiber)</li></ul>\n<h2 id=\"one-ecosystem-zero-dependencies\">One ecosystem, zero dependencies</h2>\n<p>Many previously separate packages now live in <code>effect</code> itself. The packages around it share a single version and release in lockstep. The core <code>effect</code> package has zero runtime dependencies. We control every line we ship, so there are no third-party dependency chains and less exposure to supply chain attacks.</p>\n<h2 id=\"from-functions-to-clusters\">From functions to clusters</h2>\n<p>Effect started with a much smaller scope. Today, it covers the full range, from a single function to a distributed system. People came for the programming model: an effect system with built-in typed errors, dependency injection, resource management, structured concurrency, and observability. The standard library and platform integrations grew around it. Then came higher-level primitives for distributed systems, including durable workflows and clustering. Every layer is built on that same model, with the same guarantees all the way up.</p>\n<h2 id=\"mainstream-adoption\">Mainstream adoption</h2>\n<p>Effect now runs in production at companies of all sizes, including large enterprises. Weekly npm downloads in the week of September 21, 2026 were about 43.9M, with 179× growth since 3.x. In the last 7 days, 4.x adoption already outsizes 3.x (about 56% vs 44%). Projects with communities of their own have grown around it: Alchemy for cloud infrastructure, and Foldkit for the frontend.</p>\n<h2 id=\"long-term-support\">Long-term support</h2>\n<p>Starting with this release, every major version of Effect has a long-term support policy. For Effect 4.x:</p>\n<ul><li>Bug fixes until September 2029, or one year after 5.0 ships, whichever is later</li><li>Security fixes until September 2029, or two years after 5.0 ships, whichever is later</li></ul>\n<p>Support lasts at least three years. If 5.0 ships late enough, bug and security fixes run past that minimum.</p>\n<h2 id=\"what-s-next\">What&#39;s next</h2>\n<p>The first priority is stabilizing more of the ecosystem. Some newer modules are still tagged <code>@stability unstable</code> or <code>@stability experimental</code>. Beyond that, broader native platform support and more higher-level primitives. Migrating? Start with the migration guide—hand it to your coding agent, and it should do most of the work on its own.</p>\n<p>Thank you to everyone who contributed, tested releases, reported bugs, and helped others get started.</p>","headings":[{"level":1,"text":"Effect 4.0","id":"effect-4-0"},{"level":2,"text":"One ecosystem, zero dependencies","id":"one-ecosystem-zero-dependencies"},{"level":2,"text":"From functions to clusters","id":"from-functions-to-clusters"},{"level":2,"text":"Mainstream adoption","id":"mainstream-adoption"},{"level":2,"text":"Long-term support","id":"long-term-support"},{"level":2,"text":"What's next","id":"what-s-next"}]}}