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

@debonet/bugout

v1.0.7

Published

A few tools to make debugging output to the console more bearable

Downloads

2

Readme

bugout

A few tools for making debug messages to the console more usable

Usage


	const {D, I, E} = require( `@debonet/bugout` );

	D("Hello World!");
	D("Hello World!");
	D("Hello Mars!");
	D("Hello World!");
	D("Hello World!");
	D("Hello World!");
	for (let n=0; n<1000; n++){
		I(`I'm showing ${n}`);
	}
	D("Hello World!");
	D("Hello World!");
	for (let n=0; n<1000; n++){
		D("HELLO WORLD!");
	}

Yields output

Hello World! [ 2 times]
Hello Mars!
Hello World! [ 3 times]
Hello World! [ 2 times]
HELLO WORLD! [ 1000 times]

Running the same code above but substituting IKeep for I, e.g.:

	const {D, IKeep : I, E} = require( `@debonet/bugout` );

will yield:

Hello World! [ 2 times]
Hello Mars!
Hello World! [ 3 times]
I'm showing 999
Hello World! [ 2 times]
HELLO WORLD! [ 1000 times]

API

D( values* )

debug( values* )

prints values to standard out. If a line would be repeated exactly, instead of being printed again it simply gets "[ # times ]" appended to it

I( values* )

indicate( values* )

prints values to standard out, but overwrites any imediately preceeding output from an indicate() call.

IKeep( values* )

indicate_keep( values* )

the same as I() above, but ensures that the last line is kept

E( values* )

error( values* )

Currently this is exactly console.error

Installation

npm install @debonet/bugout