API reference
Effect HTTP handlers
API reference for connecting Effront applications to Effect HTTP servers.
@effront/core/http exposes native Effect HTTP handlers with typed failures and external service requirements.
HTTP boundaries
| API | Result | Host-supplied services |
|---|---|---|
toHttpEffect(application) | A native HTTP Effect | Live request, Scope, and external application requirements |
makeHttpEffect(application) | An Effect that constructs a native HTTP Effect | External services at construction; live request and Scope at execution |
createFetchHandler(application) | (request, env, executionContext) => Promise<Response> | Fetch context. The application Layer may require only HttpRouter and HttpServerRequest. |
Ready-made native hosts are available through Node.js / Bun and Alchemy.
toHttpEffect
import { toHttpEffect } from "@effront/core/http";
import application from "./entry.effront";
export const handler = toHttpEffect(application);The input is an ApplicationDefinition<Services, ApplicationError, Requirements>.
The result is HttpApplicationEffect<ApplicationError, Requirements>, exported from @effront/core/http.
Creating the Effect does not run it or start a listener.
| Channel | Contract |
|---|---|
| Success | HttpServerResponse.HttpServerResponse |
| Error | Application and HTTP route errors, rendering and Server Function failures, PlatformError, and HTTP errors |
| Services | HttpServerRequest.HttpServerRequest, Scope.Scope, and the application's remaining external and HTTP route requirements |
Each execution acquires the application Layer for the current request.
The host must keep the request Scope alive until the body completes, fails, or is cancelled.
Wrapping response production alone in Effect.scoped can release services before a streaming body finishes.
HEAD responses have an empty body while retaining response metadata.
Content-Length values that are negative, not safe integers, or greater than 10 MiB produce 413 before application services are acquired.
Server Function POST requests also enforce a 10 MiB limit on received bytes, even without that header.
Custom HTTP route bodies without Content-Length are not universally measured by this handler.
makeHttpEffect
makeHttpEffect(application) returns a construction Effect with no typed failure.
It requires the application's external services and returns a reusable HTTP Effect with those service references captured.
The returned Effect retains the HTTP error channel and still requires the live request and request Scope.
The application Layer remains request-scoped.
- Live request services take precedence over captured services with the same key.
- Construction-time Scope, HTTP request services, router services, and Layer memoization state are excluded from capture.
- Capture neither acquires services nor extends their lifetime. Their owner must retain them through every response body that uses them.
- Completing a request does not dispose of host-owned captured services.
The Alchemy adapter provides a deferred application loader with the same capture and lifetime rules.