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

null-logtron

v2.2.0

Published

A logger that no-ops

Downloads

30

Readme

null-logtron

A logger that no-ops

Example

var NullLogtron = require("null-logtron");

var logger = NullLogtron();
logger.debug('some static string', { some: 'meta obj' })
logger.info('some static string', { some: 'meta obj' })
logger.warn('some static string', { some: 'meta obj' })
logger.error('some static string', { some: 'meta obj' })

The NullLogger does not write anywhere. It actually writes to a circular buffer in memory (pre-allocated to 50).

Using in tests

You can use the .items() method in your tests to read the records that have been written to the logger.

var NullLogtron = require('null-logtron');
var test = require('tape');

test('some module', function t(assert) {
    var logger = NullLogtron();
    var thing = new Thing({ logger: logger })

    thing.doStuff();

    var items = logger.items();
    assert.equal(items.filter(function (x) {
        return x.level === 'error'
    }).length, 1, 'thing writes to logger.error()');
    assert.end();
});

Motivation

If your writing a library you want the application developer to pass in a logger. You cannot default a logger because that breaks the unix rule of silence.

So you either need a no-op logger or you need a ton of if statements. This is a cheap no-op logger.

I've chosen to back it by a RingBuffer so that if you do REPL into your process you can inspect the log statements.

The RingBuffer only holds 50 log records so the memory overhead is trivial.

Docs

// TODO. State what the module does.

Installation

npm install null-logtron

Tests

npm test

Contributors

  • Raynos

MIT Licensed