HTTP adapter

createSacnHttpAdapter returns an Elysia plugin. It does not listen on a port, configure CORS, rate-limit, or choose an auth policy. Your host app owns deployment.

npm install @helioslx/core elysia @elysiajs/node @elysiajs/openapi

import { createSacnSource } from "@helioslx/core/node";
import { createSacnHttpAdapter } from "@helioslx/core/http";
import { Elysia } from "elysia";

const source = createSacnSource({
  name: "HTTP control",
  transportOptions: { iface: "192.168.10.20" },
  installProcessHandlers: false,
});

await source.start();

const sacn = createSacnHttpAdapter({
  source,
  prefix: "/sacn",
  auth: ({ request }) => {
    // Return false for 401, or a Response to forward.
    return request.headers.get("authorization") === `Bearer ${process.env.TOKEN}`;
  },
});

const app = new Elysia().use(sacn);
app.listen({ hostname: "127.0.0.1", port: 3000 });

Options

Canonical routes

All paths are under prefix (default /sacn).

Channel bodies accept a map or an array of writes, with optional shared or per-channel durationMs. Frame bodies use durationMs for a shared fade.

When a viewer is provided:

Deprecated /outputs… aliases still exist with deprecation headers. Prefer the /universes/…/priorities/… paths.

Host responsibilities

• Bind address (prefer 127.0.0.1 unless auth and network are locked down)
• TLS or reverse proxy
• CORS (avoid wildcards on live control)
• Rate and body-size limits
• Process signals and shutdown order when not using Node auto-handlers

The adapter owns neither the source nor the viewer. Stop the HTTP server, then close() services you own.

See the embedded HTTP example.