Dev Mode

TriFrost includes a tiny but powerful utility called isDevMode() that helps your app know: "Am I in development or production?"

This utility enables environment-aware behavior like tracing, logging, debugging, and more — and it’s runtime-agnostic.

import {isDevMode} from '@trifrost/core';

function (ctx:Context) {
  isDevMode(ctx.env); // true | false
}

It accepts your app’s env object and returns a boolean:

For Example:

if (isDevMode(ctx.env)) {
  ctx.logger.debug('Running in dev mode!');
} else {
  ctx.logger.info('Production mode – tracing enabled');
}

You can use this to toggle:

It follows a layered check strategy:

If your env contains TRIFROST_DEV, it takes priority.

Accepted values:

# .env or .dev.vars
TRIFROST_DEV=true

If TRIFROST_DEV is not set, it checks:

NODE_ENV !== 'production'

This ensures safe defaults in traditional environments.

If neither are provided, it falls back to false (production mode).

TriFrost’s internal tracing + observability changes behavior based on dev mode status:

Dev mode
All runtimes will default to using ConsoleExporter with no inclusions
Prod Mode
Node/Bun will default to using ConsoleExporter with trace_id inclusion
Workerd will default to using JsonExporter

✅ In dev mode, all runtimes fall back to ConsoleExporter to make debugging easy and consistent — even on the edge.

To ensure consistency, always explicitly set TRIFROST_DEV in your local dev environment file.

Local (Node, Bun):

# .env
TRIFROST_DEV=true

Cloudflare Workers:

# .dev.vars (wrangler)
TRIFROST_DEV=true

TriFrost Docs