effx

effx

The enterprise on-ramp to full-stack Effect. A familiar declarative surface on top, ordinary inspectable Effect underneath, no lock-in.

effx bridges traditional enterprise frameworks and full-stack Effect. You write a familiar declarative surface (decorators or builder chains). The compiler reads it ahead of time and writes ordinary Effect (HttpApi, Rpc, CLI commands, a client, Foldkit commands) that you can read, keep and edit. Effect's typed errors and requirements stay visible, and there is no effx runtime.

source ──► annotations ──► IR (Schema) ──► analyses ──► generators ──► ordinary Effect

The one rule: a decorator is a contribution to the IR, never generated behaviour. The positioning is recorded in ADR 0012.

Introduction

What effx is in the enterprise-framework frame, how it compares on one operation, and the invariants it keeps.

Coming from NestJS, ASP.NET Core or Laravel

Concept maps from each framework, with every concept marked supported, via an ecosystem package, or a gap.

Getting started

Compile the examples/users slice end to end.

Authoring

Every annotation, as a decorator and as a builder step.

CLI

effx check, build, inspect and graph.

Concepts

IR, StableId, semantic hash, emit modes, targets, external bindings.

Extensions

The Extension contract.

Diagnostics

Codes, severities, and where the registry will be generated.

Architecture decisions

The ADRs, rendered from docs/decisions.

API reference

Generated from JSDoc with @effect/docgen.

What is effx

effx is the enterprise on-ramp to full-stack Effect. You write a familiar declarative surface, the compiler writes ordinary, inspectable Effect, and nothing locks you in.