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

nite-owl

v5.0.5

Published

A debounced EventEmitter that watches for file changes

Downloads

2,600

Readme

nite-owl

package version build status

You need to watch a directory for changes, but don't want to be notified all the time? Try nite-owl.

Who watches the Nite Owl?

Before you ask: No, we didn't implement all this hairy file watching business ourselves. We simply use chokidar.

Using nite-owl basically comes down to this:

let watch = require("nite-owl");

watch(myFavoriteDirectories). // either a single directory path or an array thereof
    on("edit", myFavoriteFunction).
    on("error", myErrorFunction);

Whenever one of the files in any of myFavoriteDirectory changes, myFavoriteFunction will be invoked with the paths of all files which changed within a short interval.

This notification is debounced: You only get notified at most once every 50 milliseconds. You can adjust that value by providing a second argument to the watch function.

The error callback will be called, when watching the files resulted in an error. The most common error is the TooManyFilesError (it has the code ERR_TOO_MANY_FILES). It occurs on Linux when you watch too many files. In this case you have to either increase the inotify limits or choose to watch less files. An error handler could look like this:

watch(myFavoriteDirectories).
    on("error", err => {
        if(err.code === "ERR_TOO_MANY_FILES") {
            console.error("Watching too many files");
            process.exit(1);
        } else {
            throw err;
        }
    });

The process can also be terminated programmatically:

let watcher = watch(…);
…
watcher.terminate();

License

Licensed under Apache 2.0.