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

vertex-logger

v2.3.2

Published

A logger.

Downloads

52

Readme

npm Build Status Coverage Status

vertex-logger

A logger.

npm install vertex-logger --save

const VertexLogger = require('vertex-logger');

const logger = new VertexLogger({
  root: 'root',
  name: 'name',
  level: 'info' // off fatal error warn info debug trace
});

logger.level = 'debug'; // reset level

logger.info('interpo%s st%s', 'lated', 'ring');
// if stdout is TTY:
//   [ info] (root/name) interpolated string (201ms)
// if not:
//   2016-10-21 14:11:31.471 [ info] (root/name) interpolated string (201ms)

logger.fatal(); // to stderr
logger.error(); // to stderr
logger.warn();  // to stdout
logger.info();  // to stdout
logger.debug(); // to stdout
logger.trace(); // to stdout

logger.error("couldn't", new Error('Why'));
// [error] (root/name) couldn't (1231ms)
// Error: Why
//     at repl:1:25
//     at sigintHandlersWrap (vm.js:22:35)
//     at sigintHandlersWrap (vm.js:96:12)
//     ...

A tree of loggers...

...can be built for context.

let appLogger = new VertexLogger({
  root: 'app-name',
  name: 'application'
});

let serviceLogger = appLogger.createLogger({
  name: 'service-name'
});

let componentLogger = serviceLogger.createLogger({
  name: 'component-name'
});

//
// Log messages only display 'root/name' and not 'root/parent/parent/name'
//
// eg.

componentLogger.info('message');
// [ info] (app-name/component-name) message (0ms)

A repl

…can be registered via any logger in the tree

let logger = new VertexLogger();
let repl = require('repl').start();

logger.repl = repl; // to register the repl

// now the repl prompt will remain continuously below the latest logged message

logger.repl = undefined // to unregister the repl

// supports only one repl
// repl can be registered at any logger in the tree and will be applied to all

Loglevel functors...

...can be passed as loglevel to target specific components.

let logger = new VertexLogger({
  root: 'app-name',
  name: 'application',
  
  level: (info) => {
    if (info.name == 'specific-component') return 'trace';
    // defaults to 'info'
  }
});

// The level functor is inherited into the tree of loggers
// - it overrides log levels passed as string on createLogger() child
// - it does not override loglevels passed as functions on createLogger() child


// Level by functor can also be directly assigned

logger.level = (info) => {
  if (info.ancestors.indexOf('service-name') >= 0) return 'off';
  if (info.ancestors.pop() == 'specific-parent') return 'off';
  return 'trace';
}

Todo

parentLogger.levelAll == 'off' || fn; // applied to all children