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

pico-log

v1.0.0

Published

an incerdibly tiny javascript logging library

Downloads

2

Readme

pico-log

An incredibly tiny javascript logging library.

NPM

pico-log was inspired by the lovely package loglevel. However loglevel lacks one key feature, the ability to set your own logging functions. pico-log implements the best parts of loglevel, with this feature added.

install

npm install --save pico-log

features

  • 32 lines of code
  • Log on 5 different levels, trace, debug, info, warn, error
  • Doesn't use wrappers so it maintains stack trace integrity
  • Able to overwrite the logging function at each level
  • Attempts to use the most appropriate console function, falls back onto console.log
  • Defaults to warn level, so if you forget to set a level your production enviroment won't explode with logs

documentation

usage

    const log = require('pico-log');
    log.setLevel('info');

    log.debug('Fancy message', false, 6, { nifty : true})

logging

  • log.trace(arg1, arg2,...)
  • log.debug(arg1, arg2,...)
  • log.info(arg1, arg2,...)
  • log.warn(arg1, arg2,...)
  • log.error(arg1, arg2,...)

log.setLevel(level)

Disable logging below the specified level. level can be the following:

  • Internal log level, eg. log.levels.SILENT
  • Case-insenstive string, eg. 'error'
  • Numerical index from 0 (trace) to 5 (silent)

log.getLevel()

Returns the current log level as a number, 0 (trace) to 5 (silent).

log.levels

Access to pico-logs internal log level list, eg. log.levels.WARN == 3

overwriting log methods

To overwrite a log method, simply assign the function you want to run into the library, eg.

    log.debug = (...args)=>{
        console.log('DEBUG', ...args);
    }

    log.debug('test');

Note: After you overwrite a method, it will log regardless of the level set until log.setLevel() is called. pico-log caches the logging methods when you set the level and then switches the available methods based on the log level.

If you care about your stacktraces, try not to use wrapper functions when overwriting log methods as best as you can. They will clutter up your stacktraces.