docs/releases.md
Below is the list of items that made up the roadmap for past releases.
3.0.0silent support.3.0.0 upgrade guide: https://github.com/winstonjs/winston/blob/master/UPGRADE-3.0.mdwinston. If we cannot log at high-volume we cannot ship out of RC. There was [test coverage for this][stress-test] that should be failing, but isnt. (Fixed by #1291).docs/transports.md.winston-transport, logformwinston itselfLogger.prototype.level and Transport.level play nice(r) together.new winston.Logger in favor of winston.createLogger.TransportStream and LegacyTransportStream.TransportStream and LegacyTransportStream into winston-transport.winston/config.js to winston/config/index.jswinston.clonewinston-transportvows-based tests.
test/*-test.jstest/formats/*-test.jstest/transports/*-test.jswinston.config into triple-beam around a base Levels class.
(Fixed in [email protected])npm levels (e.g. including http).winston (currently ~72%).winston-transport.logformabstract-winston-transport.winston-compat.stream.Writable.writev in TransportStream.winston.format.colorize() format.winston.format.prettyPrint() format.winston.format.uncolorize() format.winston.format.logstash() format.winston.format.cli()ConsoleFileinfo objects
– Use triple-beam and Symbol.for('level').
winston.formats.colorize().Symbol.for('message')winston.format.padLevels() format.humanReadableUnhandledException should be the defaultwinston-compat to help with backwards compatibility for transport authors.README.md in winston.README.md for winston-transport.README.md for logform.examples/*.js to the new API.LogStream back to Logger.[email protected]winston.Container instances no longer add any transports by default.( ) from all occurances of new winston.transports.*)[email protected] in logmark.[email protected] in logmark.bunyan in logmark.pino in logmark.pino benchmarks.