Package Exports

gulplog
gulplog/index.js

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 (gulplog) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

gulplog

Logger for gulp and gulp plugins

Usage

var logger = require('gulplog');

// logs strings
logger.debug('The MOST verbose!');
logger.info('Some important info');
logger.warn('All the warnings to you');
logger.error('OH NO! SOMETHING HAPPENED!');

// supports util.format!
logger.info('%s style!', 'printf');

// log anything
logger.debug({ my: 'obj' });
logger.info([1, 2, 3]);

API

Logging (and level of logging) is controlled by gulp-cli

logger.debug(msg, ...args)

Highest log level. Typically used for debugging purposes.

If the first argument is a string, all arguments are passed to node's util.format() before being emitted.

If the first argument is not a string, all arguments will be emitted directly.

logger.info(msg, ...args)

Standard log level. Typically used for user information.

If the first argument is a string, all arguments are passed to node's util.format() before being emitted.

If the first argument is not a string, all arguments will be emitted directly.

logger.warn(msg, ...args)

Warning log level. Typically used for warnings.

If the first argument is a string, all arguments are passed to node's util.format() before being emitted.

If the first argument is not a string, all arguments will be emitted directly.

logger.error(msg, ...args)

Error log level. Typically used when things went horribly wrong.

If the first argument is a string, all arguments are passed to node's util.format() before being emitted.

If the first argument is not a string, all arguments will be emitted directly.

License

MIT