Expressjs adapts its functionality based on what type of callback you give it (this is not common in JS libraries so it is not surprising that people get confused by it). If you do this where your callback has four arguments: app.use(function(error, req, res, next) {…}); then Express assumes this is an error-only middleware handler … Read more
Winston transports have a silent property that you can set, which is probably a little nicer than removing the entire transport. I add a name to the transports to make is a little easier like this: var logger = new winston.Logger(); logger.add(winston.transports.Console, { name: ‘console.info’, colorize: true, showLevel: true, formatter: consoleFormatter, }) Then in the … Read more
When using a logger that outputs to process.stdout.write you can use “outputCapture”: “std” in the launch config to also capture that.
For winston version 3.2.0+, following will add stacktrace to log output: import { createLogger, format, transports } from ‘winston’; const { combine, timestamp, prettyPrint, colorize, errors, } = format; const logger = createLogger({ format: combine( errors({ stack: true }), // <– use errors format colorize(), timestamp(), prettyPrint() ), transports: [new transports.Console()], }); Ref: https://github.com/winstonjs/winston/issues/1338#issuecomment-482784056
As you mention, you are using 3.0.0, you can not not use winston.Logger, you may refer library code( https://github.com/winstonjs/winston/blob/master/lib/winston.js#L178 ) You need to make small update in your code, use winston.createLogger instead of new (winston.Logger) // your centralized logger object let logger = winston.createLogger({ transports: [ new (winston.transports.Console)(options.console), new (winston.transports.File)(options.errorFile), new (winston.transports.File)(options.file) ], exitOnError: false, … Read more
The default logger concept handles this nicely. Winston defines a default logger that any straight require (and subsequent require) to winston will retrieve. Thus you simply configure this default logger once, and it’s available for subsequent module use via vanilla require(‘winston’) in its glorious tweaked multi-transport mode. e.g. here is my complete logging setup that … Read more
This article does an excellent job for what you want to do. http://tostring.it/2014/06/23/advanced-logging-with-nodejs/ For your specific code you probably need something like this: var logger = new winston.Logger({ transports: [ new winston.transports.File({ level: ‘info’, filename: ‘./logs/all-logs.log’, handleExceptions: true, json: true, maxsize: 5242880, //5MB maxFiles: 5, colorize: false }), new winston.transports.Console({ level: ‘debug’, handleExceptions: true, json: … Read more
Above answers did not work for me. In case you are trying to add timestamp to your logs using the latest version of Winston – 3.0.0-rc1, this worked like charm: const {transports, createLogger, format} = require(‘winston’); const logger = createLogger({ format: format.combine( format.timestamp(), format.json() ), transports: [ new transports.Console(), new transports.File({filename: ‘logs/error/error.log’, level: ‘error’}), new … Read more