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

qlocker

v1.0.2

Published

Ordered file locks

Downloads

25

Readme

node-qlocker: Ordered file locks

This repository is part of the Joyent Triton project. See the contribution guidelines. Github pull requests are welcome.

This module allows synchronization within a single node program and across programs. Interprocess synchronization is accomplished using POSIX style exclusive write file locks. Intraprocess synchronization is accomplished by allowing only one caller at time to attempt to hold the exclusive lock on the specified file. Within a process, callers will obtain the lock in the order in which they called lock(). Interprocess ordering and fairness are not guaranteed.

Usage

lock(path, callback)

Will attempt to lock path, calling callback(err, unlock_fn) upon success or failure. If path exists, it must be writable. If path does not exist, the directory in which path will live must exist and must allow file creation.

So long as fcntl fails with EAGAIN, ENOLCK, or EDEADLK, lock will retry several times per second. If fcntl fails, the callback will be called wih a err as a non-null value. Upon success, callback will be called with an unlock function that the caller must call to release the lock.

Example

var qlocker = require('qlocker');
var path = 'a_file';

qlocker.lock(path, function lock_cb(err, unlocker) {
    if (err) {
        throw(err);
    }

    // Critical section here (lock is held)
    console.log('%s is locked', path);

    unlocker(function unlock_cb(){
        consle.log('%s is unlocked', path);
    });
}

Development

Build and sanity check with make

Any commits to this repo must comply with Joyent's style and lint requirements as well as have all unit tests passing. The easiest way to test all of these is with:

$ make

Build with npm

$ npm install

Test with npm

$ npm test

License

node-qlocker is licensed under the Mozilla Public License version 2.0. See the file LICENSE.