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 🙏

© 2026 – Pkg Stats / Ryan Hefner

debugbot

v1.2.0

Published

This is a simple Node.js program which can attach to a running Node.js program and evaluate expressions and give you the value.

Readme

Debug Bot

This is a simple Node.js program which can attach to a running Node.js program and evaluate expressions and give you the value.

Setup Instructions

Install yarn if not installed already.

npm install -g yarn
$ yarn install
$ yarn run build
$ yarn run test

This package uses Yarn 2. node_modules folder is no more. It comes with a few extra initial setup steps. VS Code is supported.

  • Make sure you select the 'Workspace version' of TypeScript.
  • A recommended extension ZipFS could be installed optionally for debugging dependencies. vscode-chrome-debug-core is already 'unplug'ged

Usage

  • Logic for using Debug Adapter is in Attacher
  • InlineExpressionEvaluator is used for the below example. An expression can be evaluated in a line in a file.
  • ExpressionEvaluator has a callback which is used when a breakpoint is hit and an expression is evaluated.
  • An instance of InlineExpressionEvaluator class can be created.
  • attach method is used to attach to a running node.js process. The debugging port has to be passed as a parameter.
  • getValue method is where a breakpoint is set and the value is fetched and returned. This needs the file path of the program where the breakpoint has to be set, line number, expression(variable name), and optionally column number.
  • disconnect can be used to disconnect the debugger.

Examples

  • tests/attacher.test.ts has the tests which is ran during npm run test
  • tests/ExpressionEvaluator/inlineEvaluatorTest.ts has a simple program which can be used as an example, shown below.

In a terminal, run :

$ yarn node --inspect=43210 ./dist/tests/sampleProgram.js

Open another terminal, run :

$ yarn node ./dist/tests/ExpressionEvaluator/inlineEvaluatorTest.js

You can see that the value is printed on the console.