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

@reactual/c

v0.1.3

Published

a node.js console.log prettifier :art:

Downloads

5

Readme

c (:art:)

A console.log prettifier for node.js

Notice

Currently under development/unreleased, not for use in production.

Installation

Published as an npm module under the @reactual organization.

yarn add @reactual/c

# or via npm

npm install --save @reactual/c

Usage

There are a few possible ways to use c within a project:

Import Directly As Needed

Import or require from @reactual/c in each file as needed. Since c is a default export, you can use any variable name you prefer.

/** ES6 imports */
import c from '@reactual/c'

/** or any var preferred */
import log from '@reactual/c'


/** ES5 require */
const c = require('@reactual/c')

/** or any var preferred */
const log = require('@reactual/c')

Logging messages

Replace normal console.log statements with examples below.

const total = 2 + 2

// console.log('The total is:', total

c('The total is:', total)

Specifying a log level

The most basic usage is to not specify a log level. c defaults to info, or error if the value being logged is an instance of a node.js Error. You can also force a specific log level by passing a 3rd argument.


const total = 2 + 2

/** level unspecified, defaults to "info" for values that aren't instances of Error */
c('info unspecified example, total:', total)

/** info, forced with abbreviation */
c('info example, total:', total, 'i')

/** info, forced with full word */
c('info, full word example, total:', total, 'info')

/** warn, forced with abbreviation */
c('warning example, total:', total, 'w')

/** error, forced with abbreviation */
c('error example, total:', total, 'e')

/** level unspecified, defaults to "error" for instances of Error */
c('error unspecified example, total:', new Error(total))

Valid values for log level, You can use the full name or abbreviation:

  • info | i
  • warn | w
  • error | e

If you pass an invalid value for level, c will ignore it and fallback to info or error depending on the value being logged.

In addition to instances of Error, the below error classes will default to the error level.

  • AssertionError
  • RangeError
  • ReferenceError
  • SyntaxError
  • TypeError