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

loge

v1.0.5

Published

Singleton logging with levels

Downloads

42

Readme

loge

latest version published to npm

My very own Node.js logging library! Crazy that no one else thought of this first!

npm install --save loge

Basic use

The singleton Logger instance defaults to writing to process.stderr.

import {logger, Level} from 'loge'

logger.level = Level.error
logger.warning('You should probably get a doctor to look at that.')
// (nothing)
logger.critical('OMG your face I you what no really just does it hurt?')
// [critical] OMG your face I you what no really just does it hurt?

Alternatively, write to process.stdout:

import {Logger, Level} from 'loge'

const logger = new Logger(process.stdout, Level.info)

Formatting

Loge's calls Node's util.format (but only when the called method's level is greater than or equal to the logger's level), so the following interpolation variables are available:

  • %s - String
  • %d - Number (integer / float)
  • %j - JSON (JSON.stringify() called without replacer or indentation

Use %% for an escaped percent sign

Levels

import {Level} from 'loge'

console.log(Level.notset)
// 0
console.log(Level.debug)
// 10
console.log(Level.info)
// 20
console.log(Level.warning)
// 30
console.log(Level.error)
// 40
console.log(Level.critical)
// 50

License

Copyright © 2014-2015 Christopher Brown. MIT Licensed.