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

node-inotify

v1.0.0

Published

inotify bindings for the new v8 javascript engine

Downloads

48

Readme

node-inotify - monitoring file system events in GNU/Linux with NodeJS

Build Status

The inotify API provides a mechanism for monitoring file system events. Inotify can be used to monitor individual files, or to monitor directories. When a directory is monitored, inotify will return events for the directory itself, and for files inside the directory. (ref: GNU/Linux Manual)

Installation

NodeJS versions 12.x.x. are currently supported and tested.

Install from NPM

    $ npm install inotify

Install from git

$ npm install node-gyp -g
$ git clone git://github.com/ldilov/node-inotify.git
$ cd node-inotify
$ node-gyp rebuild

API

  • var inotify = new Inotify(): Creates a new instance of Inotify. By default it's in persistent mode. You can specify false in var inotify = new Inotify(false) to use the non persistent mode.

  • var wd = inotify.addWatch(arg): Adds a watch for files or directories. This will then return a watch descriptor. The argument is an object as follows

    var arg = {
        // Path to be monitored.
        path: '.',
        // An optional OR'ed set of events to watch for.
        // If they're not specified, it will use
        // Inotify.IN_ALL_EVENTS by default.
        watch_for: Inotify.IN_ALL_EVENTS,
        // Callback function that will receive each event.
        callback: function (event) {}
    }

You can call this function as many times as you want in order to monitor different paths. Monitoring of directories is not recursive: to monitor subdirectories under a directory, additional watches must be created.

  • inotify.removeWatch(watch_descriptor): Remove a watch associated with the watch_descriptor param and returns true if the action was successful or false in the opposite case. Removing a watch causes an Inotify.IN_IGNORED event to be generated for this watch descriptor.

  • inotify.close(): Remove all the watches and close the inotify's file descriptor. Returns true if the action was successful or false in the opposite case.

Event object structure

var event = {
    watch: Watch descriptor,
    mask: Mask of events,
    cookie: Cookie that permits to associate events,
    name: Optional name of the object being watched
};

The event.name property is only present when an event is returned for a file inside a watched directory; it identifies the file path name relative to the watched directory.

Example of use

    var Inotify = require('inotify-remastered').Inotify;
    var inotify = new Inotify(); //persistent by default, new Inotify(false) //no persistent

    var data = {}; //used to correlate two events

    var callback = function(event) {
        var mask = event.mask;
        var type = mask & Inotify.IN_ISDIR ? 'directory ' : 'file ';
        if (event.name) {
            type += ' ' + event.name + ' ';
        } else {
            type += ' ';
        }
        // the purpose of this hell of 'if' statements is only illustrative.

        if (mask & Inotify.IN_ACCESS) {
            console.log(type + 'was accessed ');
        } else if (mask & Inotify.IN_MODIFY) {
            console.log(type + 'was modified ');
        } else if (mask & Inotify.IN_OPEN) {
            console.log(type + 'was opened ');
        } else if (mask & Inotify.IN_CLOSE_NOWRITE) {
            console.log(type + ' opened for reading was closed ');
        } else if (mask & Inotify.IN_CLOSE_WRITE) {
            console.log(type + ' opened for writing was closed ');
        } else if (mask & Inotify.IN_ATTRIB) {
            console.log(type + 'metadata changed ');
        } else if (mask & Inotify.IN_CREATE) {
            console.log(type + 'created');
        } else if (mask & Inotify.IN_DELETE) {
            console.log(type + 'deleted');
        } else if (mask & Inotify.IN_DELETE_SELF) {
            console.log(type + 'watched deleted ');
        } else if (mask & Inotify.IN_MOVE_SELF) {
            console.log(type + 'watched moved');
        } else if (mask & Inotify.IN_IGNORED) {
            console.log(type + 'watch was removed');
        } else if (mask & Inotify.IN_MOVED_FROM) {
            data = event;
            data.type = type;
        } else if (mask & Inotify.IN_MOVED_TO) {
            if ( Object.keys(data).length &&
                data.cookie === event.cookie) {
                console.log(type + ' moved to ' + data.type);
                data = {};
            }
        }
    }
    var home_dir = {
        // Change this for a valid directory in your machine.
        path:      '/home/camilo',
        watch_for: Inotify.IN_OPEN | Inotify.IN_CLOSE,
        callback:  callback
    };

    var home_watch_descriptor = inotify.addWatch(home_dir);

    var home2_dir = {
        // Change this for a valid directory in your machine
        path:      '/home/bob',
        watch_for: Inotify.IN_ALL_EVENTS,
        callback:  callback
    };

    var home2_wd = inotify.addWatch(home2_dir);

Inotify Events

Watch for:

  • Inotify.IN_ACCESS: File was accessed (read)
  • Inotify.IN_ATTRIB: Metadata changed, e.g., permissions, timestamps, extended attributes, link count (since Linux 2.6.25), UID, GID, etc.
  • Inotify.IN_CLOSE_WRITE: File opened for writing was closed
  • Inotify.IN_CLOSE_NOWRITE: File not opened for writing was closed
  • Inotify.IN_CREATE: File/directory created in the watched directory
  • Inotify.IN_DELETE: File/directory deleted from the watched directory
  • Inotify.IN_DELETE_SELF: Watched file/directory was deleted
  • Inotify.IN_MODIFY: File was modified
  • Inotify.IN_MOVE_SELF: Watched file/directory was moved
  • Inotify.IN_MOVED_FROM: File moved out of the watched directory
  • Inotify.IN_MOVED_TO: File moved into watched directory
  • Inotify.IN_OPEN: File was opened
  • Inotify.IN_ALL_EVENTS: Watch for all kind of events
  • Inotify.IN_CLOSE: (IN_CLOSE_WRITE | IN_CLOSE_NOWRITE) Close
  • Inotify.IN_MOVE: (IN_MOVED_FROM | IN_MOVED_TO) Moves

Additional Flags:

  • Inotify.IN_ONLYDIR: Only watch the path if it is a directory.
  • Inotify.IN_DONT_FOLLOW: Do not follow symbolics links
  • Inotify.IN_ONESHOT: Only send events once
  • Inotify.IN_MASK_ADD: Add (OR) events to watch mask for this pathname if it already exists (instead of replacing the mask).

The following bits may be set in the event.mask property returned in the callback

  • Inotify.IN_IGNORED: Watch was removed explicitly with inotify.removeWatch(watch_descriptor) or automatically (the file was deleted, or the file system was unmounted)
  • Inotify.IN_ISDIR: Subject of this event is a directory
  • Inotify.IN_Q_OVERFLOW: Event queue overflowed (wd is -1 for this event)
  • Inotify.IN_UNMOUNT: File system containing the watched object was unmounted

FAQ

Why inotify does not watch directories recursively?

http://www.quora.com/Inotify-monitoring-of-directories-is-not-recursive-Is-there-any-specific-reason-for-this-design-in-Linux-kernel

License

(The MIT License)

Copyright 2019 node-inotify AUTHORS. All rights reserved.

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.