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

@sandsoftwaresolutions/walk-files

v0.1.1

Published

Walk a folder in a stable order with .gitignore-style rules, never following symlinks.

Readme

@sandsoftwaresolutions/walk-files

CI

Walk a folder in the same order on every machine, with .gitignore-style ignore rules, and never follow a symbolic link. For build tools, backups, hashing, search. No dependencies.

Install

npm install @sandsoftwaresolutions/walk-files

Works with import and require(), and ships TypeScript types for both.

Usage

import { walk, listFiles, createMatcher } from "@sandsoftwaresolutions/walk-files";

const files = await listFiles("./project", {
  ignore: ["node_modules/", "dist/", "*.log", "!important.log"],
  ignoreFiles: [".gitignore"]            // also read patterns from this file in the root
});
// ["package.json", "src/index.js", "src/util/deep.js", ...]  sorted, "/" separators

for await (const entry of walk("./project", { ignore: "node_modules/" })) {
  console.log(entry.rel, entry.size, entry.mtimeMs);
}

const ignored = createMatcher(["*.log", "build/"]);
ignored("logs/app.log");      // true
ignored("build", true);       // true (second argument: is it a folder?)

Details

  • Same order everywhere. Entries are sorted by name and use / in rel, also on Windows, so a list or a hash made on one machine matches another. Names are compared as they are stored (UTF-16 order, no Unicode normalisation): macOS stores accented names decomposed, so those can sort differently there.
  • Ignored folders are skipped, not scanned. node_modules/ costs nothing.
  • Symbolic links are never followed. No loops, and nothing outside the folder is read by accident. Only the folder you pass in may itself be a link to a folder. A file that is removed while the walk runs is skipped. symlinks: "include" lists them (type "symlink") without following.
  • .gitignore rules: *, ?, [a-z], ** for any number of folders, a leading or inner / anchors to the root, a trailing / means folders only, ! re-includes (the last matching rule wins), # comments, \# and \! escapes. As in git, a file inside an ignored folder stays ignored even if a later rule says !. Patterns are matched without regular expressions, so a hostile .gitignore (*a*a*a*a*b, a dozen **/) cannot make a walk slow. A negated class such as [!a] never matches a /. CRLF line endings in the file are fine.
  • Options: dirs (also yield folders), maxDepth (1 = only the root folder), filter(entry), signal (an AbortSignal).
  • Entries: { path, rel, name, type: "file" | "dir" | "symlink", size, mtimeMs }.
  • Only the root's ignore files are read; nested .gitignore files in subfolders are not (yet).