effect-http-server

Register routes as Layers with HttpRouter.add(method, path, handler), then pass them to HttpRouter.serve and provide a platform layer like NodeHttpServer.layer(createServer, { port: 3000 }). Launch with Layer.launch and NodeRuntime.runMain.

Use HttpServerRequest.schemaBodyJson for JSON bodies, schemaBodyUrlParams for form posts, or schemaBodyMultipart for file uploads. These return Effects failing with SchemaError, which the server boundary converts to an empty 400 response automatically.

Yes, via HttpRouter.middleware, which wraps route handlers and can provide services, modify responses, or catch typed route errors declared in its handles config. Pass { global: true } to apply middleware to all routes, or provide its .layer to specific route layers.

Access request.multipart to persist file parts to temp files, or use schemaBodyMultipart with Multipart.FilesSchema for validated uploads. Control limits with the Multipart.MaxFileSize, MaxFieldSize, and MaxParts context references, and catch MultipartError to return 413.

HttpRouter is the imperative, low-level routing primitive covered here, where handlers are plain Effects returning HttpServerResponse. HttpApi is the declarative, schema-first layer with OpenAPI generation, covered by the separate effect-http-api skill.

Unhandled failures are converted at the server boundary: SchemaError becomes 400, NoSuchElementError becomes 404, and everything else becomes 500. Implement HttpServerRespondable on your error class or catch it with Effect.catchTag to control the response.