node-bunyan-lite/package.json

{
  "name": "bunyan",
  "version": "2.0.2",
  "description": "a JSON logging library for node.js services",
  "author": "Trent Mick <trentm@gmail.com> (http://trentm.com)",
  "main": "./lib/bunyan.js",
  "bin": {
    "bunyan": "./bin/bunyan"
  },

  "repository": {
    "type": "git",
    "url": "git://github.com/trentm/node-bunyan.git"
  },
  "engines": ["node >=0.10.0"],
  "keywords": ["log", "logging", "log4j", "json", "bunyan"],
  "license": "MIT",

  "dependencies": {
    "exeunt": "1.1.0"
  },
  "// dtrace-provider": "required for dtrace features",
  "// mv": "required for RotatingFileStream",
  "// moment": "required for local time with CLI",
  "optionalDependencies": {
    "dtrace-provider": "~0.8",
    "mv": "~2",
    "safe-json-stringify": "~1",
    "moment": "^2.10.6"
  },
  "devDependencies": {
    "nodeunit": "0.9",
    "ben": "0.0.0",
    "markdown-toc": "0.12.x",
    "verror": "1.3.3",
    "vasync": "1.4.3"
  },

  "scripts": {
    "test": "make test"
  }
}
first stab. 'log.info(...)' 2012-01-30 06:26:47 +00:00			`{`
			`"name": "bunyan",`
version 2.0.2 2017-08-02 23:57:02 +00:00			`"version": "2.0.2",`
doc new -c CODE; drop dtrace-provider as optionalDependency (fixes #135); add 'bunyan -0' shortcut 2014-08-01 22:57:48 +00:00			`"description": "a JSON logging library for node.js services",`
add author 2012-04-24 05:00:30 +00:00			`"author": "Trent Mick <trentm@gmail.com> (http://trentm.com)",`
first pass at a 'bunyan' cli tool for pretty printing bunyan output 2012-01-31 00:07:08 +00:00			`"main": "./lib/bunyan.js",`
			`"bin": {`
			`"bunyan": "./bin/bunyan"`
some more package.json data 2012-02-02 23:15:29 +00:00			`},`

			`"repository": {`
			`"type": "git",`
			`"url": "git://github.com/trentm/node-bunyan.git"`
			`},`
drop 0.8 support; test with iojs3.0 (tho it is broken) 2015-08-17 00:51:30 +00:00			`"engines": ["node >=0.10.0"],`
Restore dtrace-provider in optionalDependencies dtrace-provider v0.3.0 fixes build issues of yore. This fixes things for node 0.11/0.12 usage. Fixes #157 2014-10-16 05:18:11 +00:00			`"keywords": ["log", "logging", "log4j", "json", "bunyan"],`
Add license attribute https://docs.npmjs.com/files/package.json#license http://npm1k.org/ 2015-05-22 05:38:37 +00:00			`"license": "MIT",`
rev to 0.10.0 and add changelog for mhart's gzip addition 2012-06-22 05:49:04 +00:00
Correct some `bunyan` CLI exit handling. This cleans up exit handling and stdout flushing on exit after some lessons learned with https://github.com/joyent/node-exeunt This also improves internal bunyan dev debugging via the `BUNYAN_SELF_TRACE=1` envvar to help trace what was happening with the issues described in #499. Fixes #499 2017-05-04 06:21:59 +00:00			`"dependencies": {`
			`"exeunt": "1.1.0"`
			`},`
momentjs: avoid for default fast path; make required only for local time Make the default (long output format, UTC time) for the bunyan CLI a fast path that doesn't use moment.js. Admittedly I haven't measured percentage impact of `moment(rec.time).utc().format(...)` for many bunyan records. Also make moment dep optional. The bunyan CLI will error out without the moment dep only if local time is requested. 2016-02-11 06:13:01 +00:00			`"// dtrace-provider": "required for dtrace features",`
			`"// mv": "required for RotatingFileStream",`
			`"// moment": "required for local time with CLI",`
log rotation support; v0.17.0; improve README docs 2013-01-04 22:30:27 +00:00			`"optionalDependencies": {`
trentm/node-bunyan#401 mkLogEmitter closures unnecessary for disabled log levels and have perf impact 2016-10-06 22:07:44 +00:00			`"dtrace-provider": "~0.8",`
Defend against throwing defined props in stringify If an object has a defined property, that is enumerable, and this property throws an error, it will make JSON stringify throw an error, and potentially bring down the program. The solution so far is to try-catch with the usual json stringifyer, that guards against circular references. If this throws an error we will attempt to guard against defined properties; and return [Throws] if a property throws an error when accesed. The following examples illustrate the problem: ```js var obj = {}; obj.__defineGetter__('foo', function() { throw new Error('ouch!'); }); JSON.stringify(obj.foo); // error thrown ``` And using `Object.defineProperty`: ```js var obj = {}; Object.defineProperty(obj, 'foo', { get: function() { throw new Error('ouch!'); } enumerable: true // enumerable is false by default }); JSON.stringify(obj.foo); // error thrown ``` The cases we have seen in production is third party modules that has enumerable getters that try to access properties on undefined objects. Fixes #182. 2015-01-19 07:16:35 +00:00			`"mv": "~2",`
momentjs: avoid for default fast path; make required only for local time Make the default (long output format, UTC time) for the bunyan CLI a fast path that doesn't use moment.js. Admittedly I haven't measured percentage impact of `moment(rec.time).utc().format(...)` for many bunyan records. Also make moment dep optional. The bunyan CLI will error out without the moment dep only if local time is requested. 2016-02-11 06:13:01 +00:00			`"safe-json-stringify": "~1",`
			`"moment": "^2.10.6"`
log rotation support; v0.17.0; improve README docs 2013-01-04 22:30:27 +00:00			`},`
start a test suite 2012-02-08 18:05:56 +00:00			`"devDependencies": {`
drop 0.8 support; test with iojs3.0 (tho it is broken) 2015-08-17 00:51:30 +00:00			`"nodeunit": "0.9",`
fix long-stack-trace error serialization added in 0.14.4 2012-10-11 21:02:48 +00:00			`"ben": "0.0.0",`
Add 'make toc' to re-generate the TOC in the README (see #429) 2016-08-26 16:30:26 +00:00			`"markdown-toc": "0.12.x",`
[issue #139] Fix `bunyan` crash on a log record with `res.header` that is an object. 2014-05-29 07:13:01 +00:00			`"verror": "1.3.3",`
			`"vasync": "1.4.3"`
package.json: scripts.test for npm test goodness 2012-08-08 00:32:12 +00:00			`},`

			`"scripts": {`
move test suite to nodeunit 2013-01-07 19:18:12 +00:00			`"test": "make test"`
start a test suite 2012-02-08 18:05:56 +00:00			`}`
first stab. 'log.info(...)' 2012-01-30 06:26:47 +00:00			`}`