@molecule/api-error-tracking-console

Auto-generated, AI-first package reference for the molecule.dev ecosystem. It is written to be read by coding agents as much as by people, and is generated from this package's source — edit src/index.ts JSDoc, not this file.

Console (logger-based) error tracking provider for molecule.dev.

Zero-credential development default: captures are written as structured log lines through the bonded logger instead of being sent to a remote service. Swap in a remote bond (e.g. @molecule/api-error-tracking-sentry) for production without changing any consumer code.

Quick Start

import { setProvider, captureException } from '@molecule/api-error-tracking'
import { provider } from '@molecule/api-error-tracking-console'

// Bond at startup (e.g. in setupBonds()) — no credentials needed
setProvider(provider)

// Logs a structured "error-tracking: exception captured" line
captureException(new Error('boom'), { tags: { source: 'worker' } })

Type

provider

Installation

npm install @molecule/api-error-tracking-console @molecule/api-bond @molecule/api-error-tracking

API

Constants

provider

Console error tracking provider. Logs structured captures through the bonded logger and reports a generated event id, mirroring the remote providers' behavior so app code works identically in development.

const provider: ErrorTrackingProvider

Core Interface

Implements @molecule/api-error-tracking interface.

Bond Wiring

Setup function to register this provider with the core interface:

import { setProvider } from '@molecule/api-error-tracking'
import { provider } from '@molecule/api-error-tracking-console'

export function setupErrorTrackingConsole(): void {
  setProvider(provider)
}

Injection Notes

Requirements

Peer dependencies:

• @molecule/api-bond ^1.0.1
• @molecule/api-error-tracking ^1.0.1

Runtime Dependencies

• @molecule/api-bond

• @molecule/api-error-tracking

• Requires no configuration or credentials — safe in every environment.

• Each capture gets a generated event id (returned and logged), mirroring remote providers so consumer code behaves identically in development.

• setUser() scopes subsequent captures like a remote provider's user scope; flush() trivially resolves true (nothing is buffered).