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 🙏

© 2026 – Pkg Stats / Ryan Hefner

mongoose-lock-release

v0.0.3

Published

Lock Mongoose documents to ensure you're the only consumer. Release when done.

Readme

mongoose-lock-release

Lock Mongoose documents to ensure you're the only consumer. Release when done.

why?

Sometimes you want to be sure that a document gets handled (updated) once and only once. Most often that's the case because there is post-processing that should not happen more than once. If there's two or more concurrent instructions coming in for the same action (say because you're building a web server), it is very likely that all get handled, leading to duplicate post-processing behavior. This plugin enables you to make sure that only one of those processes will be able to proceed.

This is guaranteed because under the hood the atomic operation findOneAndUpdate, a wrapper for findOnAndModify, is used.

install

npm isntall mongoose-lock-release

how it works

  • with .lock(duration, callback) a document is locked until duration ms have passed, at which moment it is lockable again. If lock does not return a document in the callback, the document is locked and you should abort the process.
  • with .release(callback) a document is immediately lockable again.
  • this plugin creates a property locked on your document.

usage

Pseudo code:

  • get your model
  • lock the model
  • if it's already locked, abort
  • do all things you normally do
  • release the model

Javascript:

An example with async to handle asynchronicity.

var mongoose = require('mongoose');
var Schema = mongoose.Schema;

var MySchema = new Schema({ whatever: String });

var lockRelease = require('mongoose-lock-release');
MySchema.plugin(lockRelease, 'MySchema');

var MyModel = mongoose.model('MySchema', MySchema);

var myModel = new MyModel({whatever: 'yeah'});

require('async').series([
    function saveModel (cb) {
        //only already stored documents can be locked
        myModel.save(cb);
    },
    function lockModel (cb) {
        var duration = 10 * 1000; //10 seconds, in ms
        myModel.lock(duration, function (err, myModel) {
            //err is truthy if there's an issue unrelated to this plugin
            if (err) { return cb(err); }

            //myModel is empty if the myModel was already locked
            //otherwise, myModel is updated with the new locked time
            if (!myModel) {
                return cb(new Error('already processing myModel'));
            }
            cb();
        });
    },
    function doProcessing (cb) {
        //do whatever you want here, some great processing, post-processing, etc.
        cb();
    },
    function releaseModel (cb) {
        myModel.release(function (err, myModel) {
            //err is truthy if there's an issue unrelated to this plugin
            if (err) { return cb(err); }

            //myModel is updated with the new locked time, set to now.
            //myModel can be locked again
            cb();
        });
    },
], done);

where are the tests?

I've written tests but they require a running mongo instance. I don't know yet how to test this plugin without having to run mongo. That said, check out index.spec.js for tests that you could run if you have mongo running.