Changelog
1.3.4
log.child(...)
to work even if the logger is a sub-class
of Bunyan's Logger class.haveNonRawStreams
on <logger>.addStream
.Changelog
1.3.3
Changelog
1.3.2
JSON.stringify
throws -- possibly with an enumerable property
getter than throws. By Martin Gausby.Changelog
1.3.1
Export bunyan.RotatingFileStream
which is needed if one wants to
customize it. E.g. see issue #194.
[pull #122] Source Map support for caller line position for the "src" field. This could be interesting for CoffeeScript users of Bunyan. By Manuel Schneider.
[issue #164] Ensure a top-level level
given in bunyan.createLogger
is used for given streams
. For example, ensure that the following
results in the stream having a DEBUG level:
var log = bunyan.createLogger({
name: 'foo',
level: 'debug',
streams: [
{
path: '/var/tmp/foo.log'
}
]
});
This was broken in the 1.0.1 release. Between that release and 1.3.0 the "/var/tmp/foo.log" stream would be at the INFO level (Bunyan's default level).
Changelog
1.3.0
[issue #103] bunyan -L
(or bunyan --time local
) to show local time.
Bunyan log records store time
in UTC time. Sometimes it is convenient
to display in local time.
[issue #205] Fix the "The Bunyan CLI crashed!" checking to properly warn of
the common failure case when -c CONDITION
is being used.
Changelog
1.2.4
[issue #210] Export bunyan.nameFromLevel
and bunyan.levelFromName
. It can
be a pain for custom streams to have to reproduce that.
[issue #100] Gracefully handle the case of an unbound
Logger.{info,debug,...}
being used for logging, e.g.:
myEmittingThing.on('data', log.info)
Before this change, bunyan would throw. Now it emits a warning to stderr once, and then silently ignores those log attempts, e.g.:
bunyan usage error: /Users/trentm/tm/node-bunyan/foo.js:12: attempt to log with an unbound log method: `this` is: { _events: { data: [Function] } }
Changelog
1.2.3
Changelog
1.2.2
FATAL + 1
to turn logging off. While the standard named log levels are
the golden path, then intention was not to get in the way of using
other level numbers.Changelog
1.2.1
Changelog
1.2.0
[issue #157] Restore dtrace-provider as a dependency (in "optionalDependencies").
Dtrace-provider version 0.3.0 add build sugar that should eliminate the
problems from older versions:
The build is not attempted on Linux and Windows. The build spew is
not emitted by default (use V=1 npm install
to see it); instead a
short warning is emitted if the build fails.
Also, importantly, the new dtrace-provider fixes working with node v0.11/0.12.