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

remote-filewatcher

v0.0.5

Published

A networked drop-in replacement for filewatcher

Downloads

11

Readme

Remote Filewatcher

Build status

A networked drop-in replacement for filewatcher.

The primary use case for this module is to watch files on NFS and vboxsf mounts inside VirtualBox guests. You use the client in the guest using the same API as the original filewatcher module. And you run the server on the host OS.

Some example code for the client:

var remoteFilewatcher = require('remote-filewatcher');

var watcher = remoteFilewatcher();

watcher.add('somefile.txt');

watcher.on('change', function (file) {
    console.log('A file was changed: ' + file);
});

For the server just run remote-filewatcher ., make sure you have this module installed globally.

You can pass a directory to both the client and the server. All files will be communicated between the client and the server relative to these directories. It makes the most sense to set the client directory to the mount point inside the VirtualBox guest and to set the server directory to the exported path on the host OS. Because of the way this is implemented, change events will always have the file's absolute path as the argument, even if the file was added by a relative path.

License: MIT