npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

n4v-logger

v0.1.0

Published

Easy configurable logger class for bunyan

Downloads

1

Readme

net4VISIONS node-n4v-logger class

This is an easy configurable (based on n4v-config) class extending the bunyan logger. Supports logging of http.IncomingMessage kind requests.

Features

  • LogLevel configurable per Logger name
  • Logging to files per Logger name (optional)
  • Reopen logfiles per signal SIGINT to Node process
  • Reload logger config per SIGINT
  • HTTP request logging

Configuration

Per default the logger configuration is found in a sub-object named 'log'.

export type LogLevel = 'trace' | 'debug' | 'info' | 'warn' | 'error';

export interface ILogLevel {
  readonly level: LogLevel;
  readonly name: string;
  readonly stdoutlevel: LogLevel;
}

export interface ILoggerConfig extends IConfig {
  readonly logdir: string;
  readonly loglevelfiles?: LogLevel;
  readonly loglevels?: ILogLevel[];
  readonly loglevelstdout?: LogLevel;
  readonly logtofiles: boolean;
  readonly logtostdout?: boolean;
  readonly reopensigint?: boolean;
  readonly rereadconfigonsigint?: boolean;
}

Sample config:

{
  "log": {
    "logdir": "./test-output/",
    "loglevelfiles": "error",
    "loglevels": [{
        "level": "debug",
        "name": "testnotrace",
        "stdoutlevel": "error"
      },
      {
        "level": "debug",
        "name": "testdebug",
        "stdoutlevel": "error"
      },
      {
        "level": "debug",
        "name": "testinfodebug",
        "stdoutlevel": "error"
      },
      {
        "level": "info",
        "name": "testinfo",
        "stdoutlevel": "error"
      },
      {
        "level": "info",
        "name": "test/slash",
        "stdoutlevel": "error"
      },
      {
        "level": "info",
        "name": "test\\backslash",
        "stdoutlevel": "error"
      }
    ],
    "loglevelstdout": "error",
    "logtofiles": true,
    "logtostdout": true,
    "reopensigint": true,
    "rereadconfigonsigint": true
  }
}

Usage

TypeScript

import * as http from 'http';
import { Logger } from 'n4v-logger';

const cfgfile = './path/config.json';
const log = Logger.getLogger('test-logger', cfgfile);
const req: http.IncomingMessage;

log.reqinfo(req, 'Some message: %s', more);

JavaScript

var http = require('http');
var Logger = require('n4v-logger').Logger;

var cfgfile = './path/config.json';
var log = Logger.getLogger('test-logger', cfgfile);
var req; // http.IncomingMessage;

log.reqinfo(req, 'Some message: %s', more);

API

Logger

Logger.getLogger(name: string, configfile?: string)

Logger instance

Arguments ... can be starting with an error or an object or the format string with following params.

  • .debug(...)
  • .error(...)
  • .info(...)
  • .trace(...)
  • .warn(...)
  • .reqdebug(req, ...)
  • .reqerror(req, ...)
  • .reqinfo(req, ...)
  • .reqtrace(req, ...)
  • .reqwarn(req, ...)

And the other stuff from base bunyan logger.