Config and Logging

ConfigService

ConfigService is always available in DI.

• Without explicit schema: wraps process.env.
• With schema: configureConfig(schema, source) validates and stores typed config.

import { ConfigService } from "@smounters/imperium/services";
import { appConfigSchema, type AppConfig } from "@smounters/imperium/validation";

app.configureConfig(appConfigSchema, process.env);

const cfg = app.resolve(ConfigService<AppConfig>);
const port = cfg.get("APP_PORT");

Extending the base schema

You can extend the exported base schema in your app:

import { appConfigSchema } from "@smounters/imperium/validation";
import { z } from "zod";

const projectConfigSchema = appConfigSchema.extend({
  REDIS_URL: z.url(),
});

ConfigService methods:

• getAll()
• get(key)
• has(key)
• getOrThrow(key, message?)

LoggerService

LoggerService is injectable and uses tslog under the hood.

import { LoggerService } from "@smounters/imperium/services";

@Injectable()
class OrdersService {
  constructor(private readonly logger: LoggerService) {}

  createOrder(id: string) {
    this.logger.info({ event: "order.create", id });
  }
}

Logger Configuration

app.configureLogger({
  name: "backend",
  minLevel: 3,
  prettyLogTemplate: "{{yyyy}}-{{mm}}-{{dd}} {{hh}}:{{MM}}:{{ss}} | {{logLevelName}} |",
});

await app.start({ accessLogs: true });

• accessLogs: true enables request access logs.
• Logger can still be customized per app before startup.