@molecule/api-logger-console
Provider bond · logger · API (Node) · v1.0.2 · Apache-2.0
Console logger provider using native console methods
npm install @molecule/api-logger-consolenpm · Source on GitHub · Implements @molecule/api-logger
How it works
@molecule/api-logger-console is a provider bond on the API (Node) side: it implements the logger core interface (@molecule/api-logger) with a concrete vendor or library behind it.
Your code calls the core; you wire this provider once at startup. Swapping vendors later is one line in that wiring, not a rewrite.
import { logger, setLogger } from '@molecule/api-logger'
import { provider } from '@molecule/api-logger-console'
setLogger(provider)
logger.info('Server started on port', 3000)Works with: @molecule/api-logger
Reference
Console logger provider for molecule.dev.
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.tsJSDoc, not this file.
Quick Start
import { logger, setLogger } from '@molecule/api-logger'
import { provider } from '@molecule/api-logger-console'
setLogger(provider)
logger.info('Server started on port', 3000)
Type
provider
Installation
npm install @molecule/api-logger-console @molecule/api-logger
API
Constants
consoleLogger
Console-based logger implementation.
const consoleLogger: Logger
provider
Default console logger provider.
const provider: Logger
Core Interface
Implements @molecule/api-logger interface.
Bond Wiring
Setup function to register this provider with the core interface:
import { setLogger } from '@molecule/api-logger'
import { provider } from '@molecule/api-logger-console'
export function setupLoggerConsole(): void {
setLogger(provider)
}
Injection Notes
Requirements
Peer dependencies:
@molecule/api-logger^1.0.1
Runtime Dependencies
-
@molecule/api-logger -
The provider passes every level straight to the matching
consolemethod — minimum-level filtering happens once, in@molecule/api-logger(LOG_LEVELenv var /setLevel(), default'info'). A "missing"logger.debug(...)line means the CORE's gate dropped it — lower the gate; the provider has no level configuration of its own. -
tracedelegates toconsole.trace, which prints a stack trace with every call (console behavior, not a bug).