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

@laoban/debug

v1.4.51

Published

A general debug utility that allows debugs to be turned on and off easily and thus left in the code

Downloads

11,277

Readme

Debugging

I often find that I use 'printline debugging'. This is where we add 'console.log' lines to code in order to find defects.

In general it's a bad idea to leave these in production for a number of reasons:

  • They pollute console.log with noise making it hard to find real issues
  • They can take time (but actually usually don't)

However when logging we often have different levels of logging. In java for example we often have 'logging levels'. 'Error', 'Warn', 'Info' and debug, and then we have tools to examine the logging files.

While I don't feel the need for levels here (yet), I want the ability to 'turn on and off' debugging in parts of the code.

For example I might have a section of the code called 'generations' and I might want to have logging messages that only appear when I have a problem in the 'generations' code and want to debug it.

Setting up to use

I typically have an object I used for dependency inject. Say it's called context. I have a comma separated list of names called debugString. This is the list of 'sections' that I want debugging enabled for

let contextWithDebug=addDebug(debugString, x => console.log('#', ...x))(context)

This context was previously some object, and now it is an object with {debug: <the debug function>} added

Using

    let s = contextWithDebug.debug('generations');
    ...
    ...
    s.message(() => ['some', 'list', 'that', 'might', 'get', 'logged']
    ...
    ...
    ...s.k(() => 'about to fullfill a promise', () => <something that returns a promise>>)
  • The first line created a javascript object that will only print to the output when the debugString contains 'generations'.
  • s.message sends a message to console.log if 'generations' is in the debugString
  • s.k() returns the promise returned by <something that returns a promise>. It logs errors in that promise as well