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

stares

v1.5.5

Published

Stares is a inter-process node.js module to manage multiple file watchers.

Downloads

34

Readme

NPM version Build Status Dependency Status

Stares

Stares is a inter-process node.js module to manage multiple file watchers.

With stares, you could avoid duplicately watching a same file or directory because stares instances could share with each other even if they are in different processes.

Usage

var stares = require('stares');

stares({
    port: 9807

}).on('all', function(){
    console.log('something changes');

}).watch('package.json', function(err, info){
	console.log(info.watched); // ['/path/to/package.json'];
	console.log(info.watching); // There might be other paths.
});

stares(options)

Class: stares.Stares(options)

  • options Object
    • port Number socket port to handle processes
    • permanent Boolean=false

.watch(files, callback)

  • files Path|Array.<Path> the file(s) to be watched
  • callback function(err, info)
    • err
    • info.pid Number The process id who accepts the task to watch the files.
    • info.watched Array.<Path> The files has been added to the watching list just now. Notice that stares won't duplicately watch a certain file, so it might be different between files and info.watched
    • info.watching Array.<Path> The current watching list.

Watch a list of files. If the current process is the master, the instance will watch these files, otherwise, stares will delegate these files to the master instance to do this job.

So, if you use .watch() method in a subordinate process, the instance will never actually watch any files, but the master instance do.

.unwatch(files, callback)

Remove files from the watching list.

The difference of the arguments from .watch() is that there's no info.watched but a info.unwatched to represent the files which has been removed just now.

Event: 'watch'

Emitted when there comes a watch request

Event: 'unwatch'

Emitted when there comes a unwatch request

Event: 'listening'

Emitted if it is a master process and just listened to a port

Event: 'connect'

Emitted if connected to a master process

Events of gaze

  • all
  • added
  • changed
  • deleted
  • renamed
  • error
  • end