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

console-wizard

v1.4.3

Published

A minimal yet colorful and customizable alternative to javascript's default logger.

Downloads

3

Readme

Contents


Installation

npm install console-wizard --save
# or
yarn add console-wizard

Usage

import { logger } from 'console-wizard';

logger.error('Invalid syntax for database query!');
logger.info('Environment: Development');
logger.success('All tests passed!');
logger.warn('getDataById() has been depreciated! Use getData instead()');

Output:

image

Tables:

import { logger } from 'console-wizard';

logger.table([
  { name: 'David Lesten', age: 24, occupation: 'Full stack Developer' },
  { name: 'Mark Nimz', age: 32, occupation: 'Backend Developer' },
  { name: 'Lucy Haris', age: 28, occupation: 'Data Scientist' },
  { name: 'Joe Lewis', age: 23, occupation: 'UI/UX Designer' },
  { name: 'Robert Wilson', age: 19, occupation: 'Frontend Developer' },
]);

Output:

tables

Configuration

You can set up the user default configuration by:

import { setWizardConfig } from 'console-wizard';

setWizardConfig({
  /* Weather to include timestamp in the log */
  includeTimestamp: true,

  /* Weather to include status in the log (Ex. "ERROR", "WARN" etc) */
  includeStatus: true,
});

The above configuration would apply for all the loggers in the codebase, except for the ones that have their own configuration (more on that here: #Configuring each log statement)

Note that configuring Console Wizard is completely optional! It ships with the above configuration by default!

Configuring each log statement

Additionally, you can also configure each log statement. For example

import { logger } from 'console-wizard';

logger.info('New GET request on /v1/users', {
  includeTimestamp: false,
});

If both user default configuration (using WizardConfig class) and inline configuration are provided, the configurations are combined with inline one being superior.

Author

License

MIT License