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

mangabi-logger

v2.0.1

Published

WinstonJS logger with pre-configured transports used by mangabi.com

Downloads

17

Readme

Mangabi Logger

WinstonJS logger with defaults defaults set for use by Mangabi.com

Installation

var logger = require('mangabi-logger')

Upgrading from version 1.0 to 2.0

In version 2 the default log level names have been changed to match the syslog levels in specified in RFC5424. All logging statments should be changed, but specifically silly, verbose, warn, and fatal no longer exist on the logger object.

Defaults

Colors

logger.debug('Blue')

logger.info('Green')

logger.notice('Green')

logger.warning('Yellow')

logger.error('Yellow')

logger.crit('Magenta')

logger.alert('Magenta')

logger.emerg('Red')

Transports

Development

  • Console Transport with color and pretty-printing. LOG_LEVEL defaults to debug

Test

  • No logging unless LOG_LEVEL is set. If LOG_LEVEL is set then dev logging will be used

Production and Stage

  • Console Transport with timestamp and exception handling. LOG_LEVEL defaults to info

Customization

  • LOG_LEVEL environment variable can be set to debug, info, notice, warning, error, crit, alert, or emerg. Any logs below this level will be ignored.
  • NODE_ENV will determine which transports are used.