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

waldo

v0.0.124

Published

Semver-oriented TypeScript library skeleton.

Downloads

1

Readme

@oresoftware/waldo

GNU/BSD find kills me sometimes, so I wrote this.

install:


# for command line tools
npm install -g waldo

# for library usage
npm install waldo --save

At the command line:

Basic usage
waldo --path="."  ### lists all matching files (no dirs)

Note that if you omit the --path arg, it defaults to $PWD/.

waldo --path="." --dirs  ### lists just dirs, -d for short
waldo --path="." --dirs --files  ### lists files and dirs, -f and -d for short
Using matching
waldo --path="." -n /node_modules/   # don't match any path that has /node_modules/ in it

waldo --path="." -n ^/node_modules/   # don't match any path that starts with /node_modules/ 

waldo --path="." -n '\.js$'   # don't match any path ends that with '.js'

waldo --path="." -m '\.js$'   #  match only paths that end that with '.js'

Library Usage


import {WaldoSearch} from '@oresoftware/waldo';

new WaldoSearch({
  
  path,  // the path you which to search
  matchesAnyOf,  // array of strings or RegExp
  matchesNoneOf, // array of strings or RegExp
  dirs,   // list dirs
  files   // list files (true by default)
  
})
.search((err, results) => {

    // results is your array of strings
});

to use with ES6 Promises

=> Use the searchp() method
new WaldoSearch({...}).searchp().then(results => {

    // results is your array of strings
});