Package Exports
- webpack-log
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (webpack-log) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
[tests]: https://img.shields.io/circleci/project/github/shellscape/webpack-log.svg [tests-url]: https://circleci.com/gh/shellscape/webpack-log
webpack-log
A logger for the Webpack ecosystem.

Please consider donating if you find this project useful.
Requirements
This module requires an LTS Node version (v8.0.0+).
Install
Using npm:
npm install webpack-log --save-dev
Usage
Create a new logger and use it to log something wild:
const getLogger = require('webpack-log');
const log = getLogger({ name: 'webpack-batman' });
log.info('Jingle Bells, Batman Smells');
log.warn('Robin laid an egg');
log.error('The Batmobile lost a wheel');
log.debug('And the Joker got away');
And there will appear magic in your console:

Options
level
Type: String
Default: info
Specifies the level the logger should use. A logger will not produce output for any log level beneath the specified level. Valid level names, and their order are:
[
'trace',
'debug',
'info',
'warn',
'error',
'silent'
]
For example, If a level was passed as { level: 'warn'}
then only calls to warn
and error
will be displayed in the terminal.
name
Type: String
Default: <webpack-log>
Specifies the name of the logger to create. This value will be part of the log output prefix.
timestamp
Type: Boolean
Default: false
If true
, the logger will display a timestamp for log output, preceding all other data
unique
Type: Boolean
Default: true
If false
, the logger will use cached versions of a log with the same name. Due to the nature of the webpack
ecosystem and multiple plugin/loader use in the same process, loggers are created as unique instances by default.