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

cldebug

v2.3.0

Published

So we probably all know and love console.log() right? And we sometimes (or always) use it instead of an debugger right?

Downloads

3

Readme

ConsoleLog Debug

So we probably all know and love console.log() right? And we sometimes (or always) use it instead of an debugger right?

So why not make it enjoyable?

Demo: alt

Here are the Features

  • Keep cLog statements in your production code. It will not be printed.
  • COLORS and Unicode. What would you want more?
  • Different message types: Information (probably the most used one), error and sucess
  • kind of easy to use ↓

How to use it

Install

Install ClDebug npm install cldebug.

Init

As already mentioned your console logs will only be printed in the dev environment. To do this simply call the initClDebug function. Example:

import { initClDebug } from 'cldebug';

//Example:
if(environment === 'DEV') {
    initClDebug();
}

Usage

First of all import it:

import cLog from "cldebug";

The cLog function takes 2-3 arguments:

cLog('type', 'message/content', 'expected behavior');

Type

Information:

info, inf, if, i

Logs an information in a beautiful blue.

Error:

error, err, er, e

Logs an error in red.

Success:

sucess, suc, su, s

Green message with checkmark, great for "checkpoints".

Message / Content

Self explaining. What you would normally write console.log(HERE).

Exected behavior

Optional. Puts the defined expected behavior after the message. Example:

var number = random.nextInt(10 - 1 + 1) + min;

cLog('i', number, '5');
This is my first ever npm package, dont judge.