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

inputcheck55

v1.2.898

Published

Looks for and implements commands from input

Readme

Learning Node 2nd edition

Updates to examples for upcoming Node.js 10 release

Chapter 3

Several of the examples, both labeled (example3-x.js) and not (chap3-x.js) were out of sync. I've since put them back in order, as well as created missing example files.

The chap3-1.js no longer throws an error. Passing in console without first adding it to the Sandbox context just doesn't work, but it no longer throws an error.

The chap3-8.js generated an error because the mime module it was depended on created a breaking change from the book's earlier version. mime.lookup() has been renamed to mime.getType(). The example was modified.

There's a new version of example3-3.js, using async to remove the pyramid of doom from the chapter 2 example. Async no longer allowed the loop within the waterfall, so it has been pulled out and processed independent of the waterfall. It's a cleaner approach.

The new version is now labeled example3-6.js to match the numbering in the book.

Reminder: even though forEach is synchronous, the waterfall doesn't block, so each file is processed in parallel. The data files will be processed out of order, as you'll note from log file.

Following examples were modified to work, as is example3-1.js chap3-4.js

One new npm component is the package-lock.json file. This file is automatically generated when npm modifies either the node_modules tree or package.json. You can read more about the file at https://docs.npmjs.com/files/package-lock.json.