@holonix/browser-logger NPM

bowser-logger

npm.io

This logger can be used as a replacement for console.log(...) messages that are a ubiquitous requirement when developing browser applications.

The logger has the following useful features:

Advanced sprintf-js message formatting
Use of source maps for module & line number lookup
Integration with VSCODE, (click on a log message to open file in the editor)
Configurable color coded messages based on INFO, WARN, ERROR, etc
Optional message index
Optional message timestamp

Example output

001 09:45:05 INFO setCounter(0)                   ./src/counter.ts:5
002 09:45:10 INFO setCounter(1)                   ./src/counter.ts:5
003 09:45:10 WARN Resource low                    ./src/res_mon.ts:225

Usage

npm install @holonix/browser-logger

./utils/logger.ts

import { BrowserLog, LogLevel } from '@holonix/browser-logger'

export const logger = new BrowserLog({
  format: '{{index}} {{timestamp}} {{title}} {{message}}{{rhs}}{{file}}:{{line}}',
  dateformat: 'HH:MM:ss',
  level: LogLevel.INFO
})

export { logger, LogLevel }

./mycode.ts

import { logger, LogLevel } from './utils/logger'

// Log something

logger.info('The index is %04d', index)
logger.warn('Add token [%s ...]', 'mytoken')

// Change logging level

logger.setLevel(LogLevel.WARN)

// Disable logging

logger.setLevel(LogLevel.DISABLED)

Fields

The configuration format field is a string containing any combination, in any order, of the following fields:

{{callee}}: the log message callee, resolved from source-map

{{file}}: the log message module name, resolved from source-map

{{index}}: log message count, format can be changed by changing the configuration indexFormat field.

{{line}}: the log message module line number, resolved from source-map

{{message}}: the user supplied log message

{{pos}}: the log message module column number, resolved from source-map

{{rhs}}: A valueless token, pushes any following fields to the right hand side

{{timestamp}}: time of log message, format can be changed by changing the configuration dateformat field.

{{title}}: log message level: LOG, TRACE, DEBUG, INFO, WARN, ERROR, FATAL

For example:

format: '{{timestamp}} {{message}}{{rhs}}{{file}}:{{line}}'

Additional Configuration

The configuration object has the following additional fields.

charactersPerLine: max number of characters in formatted log message (default: 180)

preprocess: allows for custom message preprocessing prior to transport

level: the logging level, all log message of a lower level will be dismissed (default: LogLevel.INFO)

stackIndex: allow for intervening functions between the origin of the log message and the final call to the logger. For each function add one to stackIndex

transport: The log message, fully composed, is finally passed to a transport function for display. A custom transport function can be defined. The default transport is shown below:

  transport: function (data: ITransport) {
    if (data.title === LogLevel.WARN) {
      queueMicrotask(console.log.bind(console, `%c${data.output}`, "color:yellow"))
    } else if (data.level > LogLevel.WARN) {
      queueMicrotask(console.log.bind(console, `%c${data.output}`, "color:red"))
    } else {
      queueMicrotask(console.log.bind(console, data.output))
    }
  }

Enable/Disable Logging

Logging can be disabled by setting the log level to one level above the maximum valid/expected log level. This can be done in the initial logger configuration or at a later point by calling: