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

@activescott/diag

v2.0.2

Published

Yet another logging package.

Downloads

137

Readme

@activescott/diag

npm version Build Status

This is a simple wrapper around debug that allows you to use info, debug, warn, error methods that can be conditionally enabled instead of debug's sole log method.

Other than that, it attempts to differ from diag as minimally as possible.

Usage


const diag = createDiag("mine")

diag.debug(...)
diag.info(...)
diag.warn(...)
diag.error(...)

Enabling

Each logging method is simply a new debug instance with a :debug, :info, :warn, or :error postfixed to it. For example:

The line const diag = createDiag("mine") creates instances of debug with namespaces mine:debug, mine:info, mine:warn, mine:error so you can enable and disable each level with debug's normal namespace enablement/disablement DEBUG environment variable. For example:

Enable only warn and error level for the mine logger:

DEBUG=mine:warn,mine:error node ...

Enable all levels for the mine logger:

DEBUG=mine* node ...

Enable all loggers of all names:

DEBUG=* node ...

Local Testing

You can also test your shareable config on your computer before publishing by linking your module globally. Type:

npm link

Then, in your project that wants to use your shareable config, type:

npm link @activescott/diag

Alternatives: loglevel and it's associated plugins.