Add Config, Services, And Logging

This tutorial uses the current app-host/stdlib shape. Keep values static and literal when you want the compiler to extract metadata.

Start From The API Template

The api starter is a public alpha template. It is suitable for experimenting with Sloppy's backend shape, but it is not a stable API contract.

sloppy create config-api --template api
cd config-api

Add Configuration

Add a value to appsettings.json:

{
  "Greeting": "hello"
}

Read it in a handler through ctx.config:

app.get("/message/{name}", (ctx) => {
  const greeting = ctx.config.getString("Greeting", "hello");
  return Results.json({ message: `${greeting}, ${ctx.route.name}` });
});

Add A Service

Register services before routes that use them:

const builder = Sloppy.createBuilder();

builder.services.addSingleton("Clock", () => ({
  now: () => "2026-05-09T00:00:00Z",
}));

const app = builder.build();

Handlers receive the request service provider through ctx.services.

Log A Request Event

app.get("/message/{name}", (ctx) => {
  ctx.log.info("message route handled", { route: "/message/{name}" });
  return Results.json({ message: ctx.route.name });
});

Sloppy logging is structured and avoids request bodies by default.

Verify

sloppy build
sloppy doctor .sloppy
sloppy run .sloppy --once GET /message/Ada

Expected result: doctor reports Plan metadata, and a handler-capable runtime returns a JSON response for /message/Ada.