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

node-peek

v0.1.1

Published

REPL add-on for debugging and benchmarking Node applications.

Downloads

3

Readme

node-peek

REPL add-on for debugging and benchmarking Node applications.

Build Status Coverage Status

Installation

npm install --save node-peek

Once installed, require node-peek on your main server file and run node {SERVER_FILE} --repl.

DISCLAIMER: node-peek creates a small Unix socket server on your running process to allow you to connect and debug live, as well as run and alter functions you choose to expose. Because this uses extra resources and could potentially be a security risk, all node-peek methods will default to noop and the socket server will not start without the --repl flag.

You can then use peek() to expose variables to the REPL if it's running.

Setup

const peek = require('node-peek');

/* Make variables accessible to REPL. */
peek('key', value);
peek({
  anotherKey: anotherValue
});

/* Console log to all REPLs */
peek.log(obj1, obj2);

/* Close REPL */
peek.close();

/* Change REPL prompt prefix. */
// Before: $ repl >
peek.setPrompt('my-own-repl');
// After: $ my-own-repl >

/* Define custom REPL commands, identical to built-in REPL API. */
peek.defineCommand('savestate', () => {
  fs.writeFile('/tmp/statefile.json', JSON.stringify(state), () => {
    this.outputStream.write('State saved!');
  });
});

Usage

$ ./node_modules/.bin/repl

Use like the normal Node REPL with additional helpers and custom commands.

$ repl > 2 + 2
$ 4
$
$ repl > .hdump
$ Heapdump written to /tmp/heap.1485844418719.heapsnapshot

Commands

  • .gc: Forces garbage collection.
  • .hdump: Forces a heapdump to the /tmp directory.
  • .hsize: Outputs the current heap stats in bytes.
  • .hcsv: Call once to begin reading intermittent benchmarking data into a CSV file, call again to stop.

Special Thanks to

  • https://gist.github.com/TooTallNate/2209310
  • https://github.com/martinj/node-net-repl