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

cloggy

v1.0.0

Published

A minimal logger object built with debug

Downloads

3

Readme

cloggy

A minimal debugging utility to replace console statements with debug powered logging. This works well with libraries like redux-logger;

Getting Started

npm install cloggy

In your code, require cloggy and pass in a namespace for your debug statements.

import cloggy from 'cloggy';

const log = cloggy('app');

log.info('Doing something');
log.error('An error happened');
log.debug('Doing something');
log.log('Doing something');
log.warn('Doing something');

Debugging can be enabled with space or comma-delimited names in the following ways:

  • Browser: Open the browser console and set the following local storage item
    • localStorage.debug = '*'
    • localStorage.debug = '*,-not_this'
    • localStorage.debug = 'app:*,section:*'
  • Node: Set DEBUG environment variable
    • DEBUG=* node app.js
    • DEBUG=*,-not_this node app.js
    • DEBUG=app:*,section:* node app.js

For more information about debug, check out the docs.

Methods

The returned debug object contains the following namespaced log statements.

  • info
  • debug
  • log
  • warn
  • error

There's nothing really special about the different methods other than debug assigning unique colors per function.

Screenshot

Example running in redux-logger via custom logger object.

image