Changelog
v3.2.1 / 2019-01-29
createLogger
for level convenience methods (e.g. .info()
, .silly()
).
(Fixes [#1577]).Changelog
v3.2.0 / 2019-01-26
NOTE: this was our first release using Github Projects. See the 3.2.0 Release Project.
new Error(string)
throughout the pipeline(s). (Fixes [#1338], [#1486]).warn
events up to logger in
addition to error
s.readable-stream
using CRA.3.0.0
)exitOnError
.splat
behaviorwinston
and logform
.SPLAT
to formats (Fixes [#1485]).Previously splat
would have added a meta
property for any additional
info[SPLAT]
beyond the expected number of tokens.
As of logform@2.0.0
, format.splat
assumes additional splat paramters
(aka "metas") are objects and merges enumerable properties into the info
.
e.g. BE ADVISED previous "metas" that were not objects will very likely
lead to odd behavior. e.g.
const { createLogger, format, transports } = require('winston');
const { splat } = format;
const { MESSAGE, LEVEL, SPLAT } = require('triple-beam');
const logger = createLogger({
format: format.combine(
format.splat(),
format.json()
),
transports: [new transports.Console()]
});
// Expects two tokens, but four splat parameters provided.
logger.info(
'Let us %s for %j', // message
'objects', // used for %s
{ label: 'sure' }, // used for %j
'lol', ['ok', 'why'] // Multiple additional meta values
);
// winston < 3.2.0 && logform@1.x behavior:
// Added "meta" property.
//
// { level: 'info',
// message: 'Let us objects for {"label":"sure"}',
// meta: ['lol', ['ok', 'why']],
// [Symbol(level)]: 'info',
// [Symbol(message)]: 'Let us %s for %j',
// [Symbol(splat)]: [ 'objects', { label: 'sure' } ] }
// winston >= 3.2.0 && logform@2.x behavior: Enumerable properties
// assigned into `info`. Since **strings and Arrays only have NUMERIC
// enumerable properties we get this behavior!**
//
// { '0': 'ok',
// '1': 'why',
// '2': 'l',
// level: 'info',
// message: 'Let us objects for {"label":"sure"}',
// [Symbol(level)]: 'info',
// [Symbol(message)]: 'Let us %s for %j',
// [Symbol(splat)]: [ 'objects', { label: 'sure' } ] }
README.md
for awaiting logs.ConsoleTransportOptions
interface type definition.child()
method.readable-stream
to v3.0.6
.@types/node
, nyc
, and through2
.Changelog
v3.1.0 / 2018-08-22
consoleWarnLevels
property to console transport options for console.warn
browser support.tailing: true
(Fixes [#1450], [#1194]).isLevelEnabled(string)
& isXXXEnabled()
to Logger
class.package-lock.json
.colors@^1.3.2
(Fixes [#1439]).logform@^1.9.1
.diagnostics@^1.1.1
.@types/node@^10.9.3
.assume@^2.1.0
.hock@^1.3.3
.mocha@^5.2.0
.nyc@^13.0.1
.split2@^3.0.0
.Changelog
v3.0.0 / 2018-06-12
_final
from Node.js streams. (Related to winston-transport#24, Fixes [#1250]).format.transform
with try / catch (Fixes [#1261]).colorize
to address concerns in [#1095].docs/transports.md
.package-lock.json
.logform@^1.9.0
.Changelog
v3.0.0-rc6 / 2018-05-30
winston@3.0.0
File
transport core functionality. Fixes [#1194].eol
option to Stream
transport.winston.config
to triple-beam
. Expose
for backwards compatibility.winston-transport@4.0.0
which may cause incompatibilities if
your custom transport does not explicitly require winston-transport
itself.UPGRADE-3.0.md
. Add Github Issue Template.logform
, triple-beam
, and winston-transport
to latest.Special thanks to our newest
winston
core team member – @ChrisAlderson for helping makewinston@3.0.0
a reality next week!
Changelog
v3.0.0-rc5 / 2018-04-20
Buffer.alloc
and Buffer.from
instead of new Buffer
.winston@3.0.0
UPGRADE-3.0.md
3.0.0.md
into CONTRIBUTING.md
and other
improvements to CONTRIBUTING.md
humanReadableUnhandledException
is now the default message format.README.md
is correct.devDependencies
assume
to ^2.0.1
.winston-compat
to ^0.1.1
.