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

node-web-repl

v0.0.5

Published

Add a web-based read/eval/print/loop to your Node.js app (useful for debugging)

Readme

Node Web REPL

This app is currently very rough and not really usable

Add a web-based command line to your Node.js apps in a simple way. Use this to debug your apps, alter behavior on the fly, review in-app data structures, ruin everything, etc. Connect to your apps after they've been running for months and see how they're doing.

We use Node.js, Express, HTTP auth via express.basicAuth middleware, and Hogan for templating. jcubic-jquery.terminal is used for the type-in terminal code on the client side. Your input is sent via Ajax to the /api endpoint, which eval()'s you code and spits back a string.

Demo

How to use:

var webrepl = require('node-web-repl');
	// setup your app as normal
	webrepl.createServer({
		username: 'admin',
		password: 'blob1010',
		port: 11911,
		host: '127.0.0.1
	});

You'll (hopefully) now have a running web-based REPL on port 11911! See test_app.js for a full example. (More examples coming soon.)

Architecture notes

Right now Node Web REPL creates its own Express instance, instead of plugging in to your existing routes. Motivation:

  • Your existing app (to which you are adding the REPL) may not use Express.
  • Separating the port numbers makes it safer against scanning (possibly).
  • I can't assume that your Express app is using the same view system that mine is.
  • Eventually, we may stop using Express entirely. Our needs are simple.

The Future

  • Hook console.log so you can view your console output via a web browser
  • UI/UX cleanup - make it look slightly less like garbage
  • Visual data browser (scope out 'global' and descend from there)
  • Profile on the fly
  • View Node.js's memory usage
  • Autocomplete
  • MySQL console?
  • Memcache console?

Author

Written by Thomas Lackner (@tlack) and sponsored by .CO