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

@lukebayes/each-file

v1.0.0

Published

Enhancements for node's basic file utils

Downloads

3

Readme

each-file

This is a set of utilities that extend the nodejs fs module to provide the following features:

  • Incremental notifications as files are encountered AND
  • Notifications when all iterations are complete
  • Minimizes work done in cases where some subset of available files are needed
  • Ability to read only files that have names that match a given expression
  • Asynchronous, incremental file handling

The initial use-case is a test library. Imagine a scenario where we have tens of thousands of files spread over a relatively deep file system tree. We do not want to wait for phased file system traversal to complete in order to begin executing tests, and we also want to know when all files have been examined.

This library started life as a question on Stackoverflow and quickly became a gist and eventually felt useful enough to get into a slightly more shareable form.

Examples

var eachFile = require('@lukebayes/each-file');

// Get all files (not directories) forward of ./test
eachFile('./test', function(err, file, stat) {
  if (err) throw err;

  console.log('File:', file, stat);
});


// Get all files (not directories) forward of ./test with a name that matches
// the provided regular expression.
eachFile.matching(/_test.js/, './test', function(err, file, stat) {
  if (err) throw err;

  console.log('Matched File:', file, stat);
});


// Read the contents of each file forward of ./test that matches the provided
// regular expression.
eachFile.readMatching(/_test.js/, './test', function(err, file, stat, body) {
  if (err) throw err;

  console.log('Body:', body);
});