Consider using pino instead of winston for logging

[0x2b3bfa0]

It could be a better option, not only because of asthetics, but also because of functionality and apparent project health. Configured logger objects can be passed as suggested on pinojs/pino#1108 (comment).

See also

• Unify commands and centralize logging #703 (comment)
• Unify commands and centralize logging #703 (comment)
• Provide a default logger as part of the pino module pinojs/pino#1108 (comment)

[0x2b3bfa0]

Try–it–yourself comparison

const pino = require('pino');
const winston = require('winston');

const pinoLogger = pino(
  {
    prettyPrint: {
      ignore: 'pid,hostname',
      translateTime: true,
      colorize: true
    },
    level: 'debug'
  },
  process.stderr
);

const winstonLogger = winston.createLogger({
  level: 'debug',
  format: winston.format.combine(
    winston.format.colorize(),
    winston.format.timestamp({ format: 'YYYY-MM-DD HH:mm:ss.SSS ZZ' }),
    winston.format.simple()
  ),
  transports: [
    new winston.transports.Console({
      stderrLevels: Object.keys(winston.config.npm.levels)
    })
  ]
});

for (logger of [pinoLogger, winstonLogger]) {
  logger.error(new Error('runners are exhausted because of cloud altitude'));
  logger.warn('the personal access token has been written backwards');
  logger.info('no bot dared to comment on your last commit');
  logger.debug('this repository contains files');
}

Pino

Winston

[DavidGOrtega]

I do not understand what do you want to showcase with this example. Whats the main difference?

[0x2b3bfa0]

1. Full and readable stack traces for errors
2. Object formatting

[dacbd]

p3-cool-if-someone-is-really-bored-on-a-weekend or p4-graveyard?

[0x2b3bfa0]

p5-low-priority-enough-to-postpone-choosing-a-priority