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

bugzapper

v1.0.3

Published

Simple bug zapping for your node application.

Downloads

11

Readme

node-bugzapper

Simple bug zapping for your node application.

Example

const BugZapper = require("bugzapper");
const bz = new BugZapper({
    showFileName: true
});

function checkDoor(isBarred) {
    bz.var({isBarred})
    if (isBarred) {
        bz.pt
        return "move on"
    } else {
        bz.ptm("The door should never be unbarred")
        return "open"
    }
}

checkDoor(true)
// door.js - Line 6 fired: isBarred = true
// door.js - Point fired at line 9

checkDoor(false)
// door.js - Line 6 fired: isBarred = false
// door.js - Point fired at line 12: The door should never be unbarred

Options

// With Defaults
const bz = new BugZapper({
    showFileName: false, // Show name of file.
    fullFilePath: false // Show the entire path to file.
    pointMessage: "Point fired at line %l" // Redefine the message for bz.pt and bz.pt(), %l = line number
    varMessage: "Line %l fired: %k = %v" // Redefine the message for bz.var(), %l = line number, %v = the variables mapped as name = value, ...
    alterVarLN: -1 // Offset the line number shown for bz.var() compared to its location in the code + (moves down) or - (moves up)
    alterPtLN: 0 // Offset the line number shown for bz.pt and bz.pt() compared to their location in the code + or -
})

pt

bz.pt - Mark a point in your code to be logged when it is reached.
bz.pt; // myfile.js - Point fired at line 152

ptm()

bz.ptm(<Your Message>) - Mark a point in your code to be logged with a message when it is reached
bz.ptm("This should never happen"); // myfile.js - Point fired at line 892: This should never happen

var()

bz.var({variable[, ...]}) - Mark a variable in your code to have its name and value logged when it is reached, must be an object,
let myVar = true
let myFalseVar = false
bz.var({myVar, myFalseVar}) // myfile.js - Line 536 fired: myVar = true, myFalseVar = false