Console logger - use console.log instead of process.stdout.write?

I noticed that you write to process.stdout.write instead of console.log here: https://github.com/winstonjs/winston/blob/master/lib/winston/transports/console.js#L121, and I see in issues like this - https://github.com/Microsoft/vscode/issues/19750 - that process.stdout.write isn’t sent over the v8-inspector debug protocol socket. So if users are using vscode or chrome devtools to debug Node, they won’t see those messages. If you use console.log instead, they will see them. Is there anything blocking you from using console.log instead?

[sgronblo]

This seems to affect Lambdas as well…

What’s wrong with just making this configurable?

[luatnd]

After failed with node-bind-std-to-console. I end up with this solution:

logger.add(supportNodeInspect(new winston.transports.Console({
        format: winston.format.simple()
      })));

/**
 * Override the winston console transport to support node --inspect, nodemon --inspect
 * Because winston will use stdout, stderror with higher priority than console.log
 */
function supportNodeInspect(winstonTransportsConsoleInstance) {
  const originLog = winstonTransportsConsoleInstance.log.bind(winstonTransportsConsoleInstance);

  // Override log fn to support log to node --inspect
  winstonTransportsConsoleInstance.log = (info, callback) => {
    originLog(info, callback);

    const {
            level,
            message,
            [LEVEL]: l,
            [MESSAGE]: m,
            [SPLAT]: s,
            ...meta
          } = info;
    console[level in console ? level : 'log'](message, meta);
  }

  return winstonTransportsConsoleInstance;
}