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 🙏

© 2025 – Pkg Stats / Ryan Hefner

debugview

v0.0.4

Published

Language-agnostic debugging widgets based on print statements

Downloads

12

Readme

debugview

Language-agnostic debugging widgets based on print statements.

The idea is that you often use log statements while you're debugging, really lightweight stuff like System.out.println("new value: " + val) to make sure that your code does what you think it does. But because you print to a console, the "widgets" you can use are fairly primitive:

  • Notification / status indicator. Example (JavaScript): console.log('loading data...')
  • List. Example (Java): list.stream().forEach(System.out.println)
  • Table. Example (OCaml): List.iter (fun (a, b) -> print_endline (a ^ "\t" ^ b)) list

debugview lets you add special commands to your log statements that give you easy access to a broader widget library:

  • HTML. Example (C): printf("<<<html <h2>Now the fun part...</h2> >>>\n"); adds a row to a table
  • (Aligned) Table. Example (JavaScript): console.log('<<<tr ' + fields.join('|') + '>>>') adds a row to a table
  • Bar chart. Example (JavaScript): console.log('<<<bar ' + value + '>>>') adds a bar to a bar chart

Installation

npm install -g debugview

Usage: Language-agnostic

Just pipe your program through debugview. Your program's output will still show in the terminal, but it will launch a web browser that shows the same content with all the debugview commands interpreted as tables, bar charts, etc.

$ yourprogram | debugview

If you want to see it go, try an example:

$ node example01.js | debugview

Usage: Browser JavaScript

Start debugview in remote mode:

$ debugview --remote

It will print a <script> tag for you to insert in your page. When you load the page, debugview will open a new browser window to show the log in.

The Future

debugview barely exists. I wrote just enough to convince myself it could work, so it's pretty hacky and under-documented. See TODO.markdown for things I'm planning.