Bunyan

Latest version: v0.1.2

Safety actively analyzes 630052 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 18

0.23.1

- [pull 125, pull 97, issue 73] Unref rotating-file timeout which was
preventing processes from exiting (by https://github.com/chakrit and
https://github.com/glenn-murray-bse). Note: this only fixes the issue
for node 0.10 and above.

0.23.0

- [issue 139] Fix `bunyan` crash on a log record with `res.header` that is an
object. A side effect of this improvement is that a record with `res.statusCode`
but no header info will render a response block, for example:

[2012-08-08T10:25:47.637Z] INFO: my-service/12859 on my-host: some message (...)
...
--
HTTP/1.1 200 OK
--
...

- [pull 42] Fix `bunyan` crash on a log record with `req.headers` that is a *string*
(by https://github.com/aexmachina).

- Drop node 0.6 support. I can't effectively `npm install` with a node 0.6
anymore.

- [issue 85] Ensure logging a non-object/non-string doesn't throw (by
https://github.com/mhart). This changes fixes:

log.info(<bool>) TypeError: Object.keys called on non-object
log.info(<function>) "msg":"" (instead of wanted "msg":"[Function]")
log.info(<array>) "msg":"" (instead of wanted "msg":util.format(<array>))

0.22.3

- Republish the same code to npm.

0.22.2

Note: Bad release. The published package in the npm registry got corrupted. Use 0.22.3 or later.

- [issue 131] Allow `log.info(<number>)` and, most importantly, don't crash on that.

- Update 'mv' optional dep to latest.

0.22.1

- [issue 111] Fix a crash when attempting to use `bunyan -p` on a platform without
dtrace.

- [issue 101] Fix a crash in `bunyan` rendering a record with unexpected "res.headers".

0.22.0

- [issue 104] `log.reopenFileStreams()` convenience method to be used with external log
rotation.

Page 7 of 18

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.