Environment-agnostic, ESM-friendly logger for simple needs.
npm install @open-draft/loggerEnvironment-agnostic, ESM-friendly logger for simple needs.
I've been using debug for quite some time but wanted to migrate my projects to better ESM support. Alas, debug doesn't ship as ESM so I went and wrote this little logger just for my needs. You will likely see it printing useful data in Mock Service Worker and beyond.
``sh`
npm install @open-draft/logger
This package has the same API for both browser and Node.js and can run in those environments out of the box.
`js
// app.js
import { Logger } from '@open-draft/logger'
const logger = new Logger('parser')
logger.info('starting parsing...')
logger.warning('found legacy document format')
logger.success('parsed 120 documents!')
`
Logging is disabled by default. To enable logging, provide the DEBUG environment variable:
`sh`
DEBUG=1 node ./app.js
> You can also use true instead of 1. You can also use a specific logger's name to enable logger filtering.
- Class: Loggernew Logger(name)
- logger.debug(message, ...positionals)
- logger.info(message, ...positionals)
- logger.success(message, ...positionals)
- logger.warning(message, ...positionals)
- logger.error(message, ...positionals)
- logger.extend(name)
- logger.only(callback)
-
- name string the name of the logger.
Creates a new instance of the logger. Each message printed by the logger will be prefixed with the given name. You can have multiple loggers with different names for different areas of your system.
`js`
const logger = new Logger('parser')
> You can nest loggers via logger.extend().
- message stringpositionals
- unknown[]
Prints a debug message.
`js`
logger.debug('no duplicates found, skipping...')
``
12:34:56:789 [parser] no duplicates found, skipping...
- message stringpositionals
- unknown[]
Prints an info message.
`js`
logger.info('new parse request')
``
12:34:56:789 [parser] new parse request
- message stringpositionals
- unknown[]
Prints a success message.
`js`
logger.success('prased 123 documents!')
``
12:34:56:789 ✔ [parser] prased 123 documents!
- message stringpositionals
- unknown[]
Prints a warning. In Node.js, prints it to process.stderr.
`js`
logger.warning('found legacy document format')
``
12:34:56:789 ⚠ [parser] found legacy document format
- message stringpositionals
- unknown[]
Prints an error. In Node.js, prints it to process.stderr.
`js`
logger.error('failed to parse document')
``
12:34:56:789 ✖ [parser] failed to parse document
- prefix string Additional prefix to append to the logger's name.
Creates a new logger out of the current one.
`js
const logger = new Logger('parser')
function parseRequest(request) {
const requestLogger = logger.extend(${request.method} ${request.url})`
requestLogger.info('start parsing...')
}
``
12:34:56:789 [parser] [GET https://example.com] start parsing...
Executes a given callback only when the logging is activated. Useful for computing additional information for logs.
`jsdocument size: ${documentSize}
logger.only(() => {
const documentSize = getSizeBytes(document)
logger.debug()`
})
> You can nest logger.* methods in the callback to logger.only().
You can specify the log levels to print using the LOG_LEVEL environment variable.
There are the following log levels:
- debuginfo
- success
- warning
- error
-
> Providing no log level will print all the messages.
Here's an example of how to print only warnings:
`js
// app.js
import { Logger } from '@open-draft/logger'
const logger = new Logger('parser')
logger.info('some info')
logger.warning('some warning')
logger.error('some error')
`
`js`
LOG_LEVEL=warning node ./app.js
``
12:34:56:789 ⚠ [parser] some warning
You can only print a specific logger by providing its name as the DEBUG environment variable.
`js
// app.js
import { Logger } from '@open-draft/logger'
const appLogger = new Logger('app')
const parserLogger = new Logger('parser')
appLogger.info('starting app...')
parserLogger.info('creating a new parser...')
`
`sh`
DEBUG=app node ./app.js
```
12:34:56:789 [app] starting app...