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

cuvva-log

v0.12.2

Published

Super simple standardized logging used by all Cuvva systems

Downloads

3,381

Readme

cuvva-log

Super simple logging system used by all Cuvva systems

NPM Version Build Status Coverage Status

var log = require('cuvva-log');

log.debug('hello_world');

var reason1 = log.info('bad_email');
var reason2 = log.info('bad_phone');
log.warn('some_problem', [reason1, reason2], { foo: 'bar' });

throw log.error('something_serious');

Installation

$ npm install

Usage

If you have a traditional Error object, it can be coerced into a CuvvaError:

var error; // existing traditional Error

var coerced = log.CuvvaError.coerce(error);
log.warn(coerced);

When traditional Error objects are provided as reasons, they're coerced automatically:

var error; // existing traditional Error

log.warn('some_problem', [error]);

Testing

Install the development dependencies first:

$ npm install

Then the tests:

$ npm test

Support

Please open an issue on this repository.

Authors

  • Jack Fransham

License

MIT licensed - see LICENSE file