effect-http-server

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

Use HttpServerRequest.schemaBodyJson for JSON bodies, schemaBodyForm for multipart or url-encoded forms, and HttpRouter.schemaParams for path and search params. These return Effects that fail with SchemaError, which the server maps to a 400 response automatically.

Yes, via HttpRouter.middleware, which wraps route handlers and can provide services or handle typed errors. Pass { global: true } to apply middleware to all routes, and use built-ins like HttpMiddleware.cors, logger, and tracer.

Read request.multipart to persist file parts to temp files, or use HttpServerRequest.schemaBodyMultipart with Multipart.FilesSchema for validated uploads. Enforce limits with Multipart.MaxFileSize and related Context references, catching MultipartError to return 413.

HttpRouter.serve builds the router from route Layers, adds logging and tracing, and runs it on the provided platform server. HttpServer.serve is lower-level, accepting any Effect that produces an HttpServerResponse without router features.

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