Skip to content

This Week in Effect - 129

Ziverge becomes the first official Effect Adoption Partner. Talks from Effect Miami 2 on Effective State Machines, NestJS migration, and agentic runtimes.

Hi Effecters!

Welcome back to This Week In Effect, your weekly update of the latest developments in the Effect community and ecosystem.

Effect is the TypeScript library for the AI era, helping developers build complex, synchronous, and asynchronous programs. One key feature that sets Effect apart is how it leverages structured concurrency to provide features such as async cancellation and safe resource management, making it easier to build robust, scalable, and efficient programs.

To get started, below you’ll find links to our documentation and our guide for installing Effect. Enjoy!

Recent major updates:

Technology

Effect v4 Beta updates

A landmark week for the v4 beta, with native Deno support landing in full, a broad security hardening sweep, deep fiber runtime fixes, and the v4 API docs going live on Cloudflare Pages.

  • Native Deno support: Added a full Deno platform integration in @effect/platform-deno, including HTTP platform, HTTP server, socket support, socket server, cluster HTTP and socket support, multipart support, and a Deno services aggregate module. Effect now has first-class support for Deno alongside Node.js, Bun, and the browser.

  • Fiber runtime hardening: Fixed pending interrupt delivery across interruptibleMask, prevented concurrent traversal daemon leaks, fixed FiberHandle.clear race, cleaned up Fiber.joinAll observers on interruption, preserved stack annotations for terminal root failures, stored interruptor stack frames separately, avoided runSyncExit dispatcher allocation, and made awaitAllChildren child selection linear.

  • Security hardening: Stripped credentials on cross-origin HTTP redirects, hardened cookie attribute validation, secured MSSQL transport defaults, hardened file-backed key-value store keys, hardened JSON-RPC message classification, and escaped control characters in CLI error messages.

  • v4 API docs: Deployed the v4 API documentation to Cloudflare Pages, making the full Effect v4 API reference publicly accessible for the first time.

  • Migration tooling: Added API diff tooling for v3-to-v4 migration, making it easier to identify breaking changes when upgrading.

  • Schema & encoding: Deduplicated JSON Schema fallback definitions, optimized Schema.Class decoding, refactored SchemaRepresentation, fixed dynamic record property assignment, simplified Optic composition, and emitted MCP tool output schemas.

  • Atoms & reactivity: Added custom equality detection for atoms to prevent unnecessary re-renders, and fixed atom dependencies during batch rebuilds.

  • OpenTelemetry: Preferred explicit OTLP resource configuration over implicit detection.

  • HTTP & SSE: Bounded pending SSE decoder state, fixed generated SSE event decoding, fixed FileSystem.watch recursive control, and prevented SQL runner lock refreshes from hanging.

  • AI: Fixed OpenAI compat parallel tool calls, fixed encoding of system messages as input text, and added platform literal to HttpPlatform.

  • CLI: Fixed end-of-options operands for subcommands, fixed positional argument overflow, and escaped control characters in error output.

  • Bun: Constructed empty Bun multipart streams per-request to prevent cross-request state contamination.

  • Documentation: Fixed error names in JSDoc comments, documented ChildProcess environment behavior, and migrated docgen.

You can follow the full changelog in the effect repository.

To catch up on more updates, check out Effect v4 Beta updates.


Other technical changes from the past week.

Effect Core

Effect CLI

Effect Experimental

Effect Platform

Effect Printer

Effect RPC

Effect SQL

General Chores

Effect Adoption Partner

We’re thrilled to announce Ziverge as the first Effect Adoption Partner, and they’ve also launched an Effect Training Workshop.

Community Highlights

Cause & Effect Podcast

Don’t forget to listen to our Cause & Effect podcast hosted by Johannes Schickling and available on YouTube, X(Twitter), and audio platforms like Spotify and Apple Podcast.

Devin Jameson joined Johannes Schickling on the Cause & Effect podcast to talk about Foldkit, an Effect-first frontend framework he’s been building, inspired by Elm architecture. Devin and Johannes discussed why Foldkit takes a schema-first approach to frontend state, how it differs from React, how commands model side effects, and why this architecture may be especially useful in the age of AI-assisted coding.

Play

Effect Team Content Update

  • Effect Office Hours 39 🔥
Play
  • Typed Agentic Runtimes & Workflows | Ariel Azoulay | Effect Miami 2
Play
  • How to switch to Effect for NestJS devs | Serge Leon | Effect Miami 2
Play
  • Effective State Machines with XState | David Khourshid | Effect Miami 2
Play

Effect Job Opportunities

Looking for a role where you can work with Effect? We now have a dedicated Effect jobs page with open roles from companies using Effect. We’ll keep it updated as new opportunities come in.

Explore Effect job opportunities →

Disclaimer: Please note that these job postings are shared for informational purposes, and we encourage applicants to verify details directly with the hiring companies.

Effect Merch Store

The Effect Merch Store offers a selection of Effect-branded items designed for the community. All orders are processed and fully managed through Printful.

Closing Notes

That’s all for this week. Thank you for being a vital part of our community. Your feedback is highly valued as we fine-tune this format. Feel free to share your thoughts, and we’ll do our best to tailor it to the needs of our community.

Effect Community Team

Share

Last updated

// Effect Community

Join the conversation on Discord

Meet engineers running Effect in production.