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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@aftonbladet/logger

v1.1.1

Published

A wrapper around creating bunyan loggers and streams based on hierarchical log names

Downloads

120

Readme

Logger

Build Status

A wrapper around creating bunyan loggers and streams based on hierarchical log names.

Usage

Minimal example that logs on stdout on level error:

import Logger from '@aftonbladet/logger';

const log = new Logger().getLogger('default');
log.error('Hello world');

Example with configuration:

import { Logger } from '@aftonbladet/logger';
import { defaultLogLevel, logLevels, streams, serializers } from './config';

const logger = new Logger({
    defaultLogLevel,
    logLevels,
    streams,
    serializers,
});

const log = logger.getLogger('myapp.server');

…

log.debug('Initializing %s', thing);

…

log.error(err, 'Failed to do that thing');

Configuration

Example config.js:

export const defaultLogLevel = 'error';
export const logLevels = {
    myapp: 'error',
    'myapp.shared': 'info',
    'myapp.shared.specific': 'fatal',
    'myapp.server': 'warn',
};

export const streams = [
    {
        type: 'rotating-file',
        path: `${logDir}/hyperion.log`,
        period: '1d',
        count: 7,
        level: 'trace',
    },
];

Developing

  1. Optional step (if not logged in already): ./npm login --registry=https://registry.npmjs.org/ --scope=@aftonbladet
    • username is aftonbladet
    • password can be found in https://password.int.aftonbladet.se:1583/PassTrixMain.cc (search for npm)
    • email is [email protected]
  2. npm install

Release and Publish

Every push to master will result in a new patch release being tagged and published on npmjs.org.

If you want to bump the minor or major version, just use the npm version command as you please. The version will be tagged and pushed automatically and Travis will publish it on npmjs.org.

E.g if you are on version 1.0.4 and run:

npm version minor

Travis will publish 1.1.0 on npmjs.org for you.