Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

bunyan

Package Overview
Dependencies
Maintainers
1
Versions
112
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

bunyan - npm Package Versions

1
12

1.3.4

Diff

Changelog

Source

1.3.4

  • Allow log.child(...) to work even if the logger is a sub-class of Bunyan's Logger class.
  • [issue #219] Hide 'source-map-support' require from browserify.
  • [issue #218] Reset haveNonRawStreams on <logger>.addStream.
trentm
published 1.3.3 •

Changelog

Source

1.3.3

  • [pull #127] Update to dtrace-provider 0.4.0, which gives io.js 1.x support for dtrace-y parts of Bunyan.
trentm
published 1.3.2 •

Changelog

Source

1.3.2

  • [pull #182] Fallback to using the optional 'safe-json-stringify' module if JSON.stringify throws -- possibly with an enumerable property getter than throws. By Martin Gausby.
trentm
published 1.3.1 •

Changelog

Source

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).

trentm
published 1.3.0 •

Changelog

Source

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.

trentm
published 1.2.4 •

Changelog

Source

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] } }
    
trentm
published 1.2.3 •

Changelog

Source

1.2.3

trentm
published 1.2.2 •

Changelog

Source

1.2.2

  • Drop the guard that a bunyan Logger level must be between TRACE (10) and FATAL (60), inclusive. This allows a trick of setting the level to 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.
trentm
published 1.2.1 •

Changelog

Source

1.2.1

  • [issue #178, #181] Get at least dtrace-provider 0.3.1 for optionalDependencies to get a fix for install with decoupled npm (e.g. with homebrew's node and npm).
trentm
published 1.2.0 •

Changelog

Source

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.

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc