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

log-count

v1.2.0

Published

Wrapper for console.log with several log levels

Downloads

9

Readme

log-count

npm version Downloads per month Build status

Classes

Logger - in your code, log messages at several different levels. Have the ability to change the logging level on the Logger instance so that only messages of certain importance are shown.

Quick start

Do npm install log-count in your Javascript npm project directory. Then in a Javascript file:

// Importing
import { Logger } from 'log-count';

// Default constructor
const defaultLog = new Logger();
defaultLog.success('You have successfully displayed a success-level message using log-count');

// Constructing
const logger = new Logger({
  level: 7,
  shy: false,
  hideLevel: false,
});

// Logging
logger.fatal('A fatal error');
logger.error('An error');
logger.warn('A warning');
logger.success('A success');
logger.info('An info');
logger.debug('A debug');
logger.trace('A trace');
logger.debug({ text: 'Text can be supplied as an object' });
logger.success({ obj: { or: 'you', can: 'directly log', any: 'object' } });

// Counting
console.log(logger.count) // {}  // Empty object
logger.info({ type: 'myType' });
logger.error({ type: 'myTypeB' });
logger.debug({ type: 'myTypeB' });
console.log(logger.count) // { myType: 1, myTypeB: 2 }  // Each type gives a separate counter

Constructor options

new Logger({ level, shy, hideLevel });

level: integer, from 0 to 7

  • 0: log nothing
  • 1: only log fatal
  • 2: previous levels + errors
  • 3: previous levels + warnings
  • 4: previous levels + successes
  • 5: previous levels + info
  • 6: previous levels + debug
  • 7: previous levels + trace

shy: boolean

  • false: (default) logger prefixes its messages with its own name, helps to know how many loggers there are, which one is speaking
  • true: logger doesn't give its name when logging

hideLevel: boolean

  • false: (default) logger always shows the message level
  • true: logger hides the level if is below FATAL, ERROR or WARNING