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

locko

v1.1.0

Published

A simple in-process locking mechanism for critical sections of code.

Downloads

46,027

Readme

Locko

Locko is a small package for implementing exclusive locking on critical sections of code.

When to use

Use locko when you need to ensure that only one "thread" can be inside of a section of code at once. Consider the following code.

const util = require('util');
const sleep = util.promisify(setTimeout);

async function print() {
  console.log('First');
  await sleep(100);
  console.log('Second');
  await sleep(100);
  console.log('Third');
}

print();
print();
print();

Without locko, this will print:

First
First
First
Second
Second
Second
Third
Third
Third

Now add locko:

const util = require('util');
const sleep = util.promisify(setTimeout);

async function print() {
  await locko.lock('print');

  console.log('First');
  await sleep(100);
  console.log('Second');
  await sleep(100);
  console.log('Third');

  locko.unlock('print');
}

print();
print();
print();

This will now print:

First
Second
Third
First
Second
Third
First
Second
Third

A real world example

It's often the case that you need to both read and write to a file, but without any kind of synchronization strategy, it's possible to read from a file while it's being written, or write to a file while it's being read, or have more than one writer writing at once. This is very likely to cause failures in an application.

Using locko you can ensure that no more than one operation is being executed on a file at any given time.

async function readFile(filePath) {
  await locko.lock(filePath);

  return new Promise((fulfill, reject) => {
    fs.readFile(filePath, (err, content) => {
      locko.unlock(filePath);

      if (err) {
        reject(err);
      } else {
        fulfill(content);
      }
    }); 
  }); 
}

async function writeFile(filePath, content) {
  await locko.lock(filePath);

  return new Promise((fulfill, reject) => {
    fs.writeFile(filePath, content, (err) => {
      locko.unlock(filePath);

      if (err) {
        reject(err);
      } else {
        fulfill();
      }
    });
  });
}

Best practices

If you never unlock the lock, it will remain locked forever. Therefore you should usually use a try-finally to ensure that the lock gets released. For example:

async function print() {
  try {
    await locko.lock('print');

    console.log('First');
    await wait(100);
    console.log('Second');
    await wait(100);
    console.log('Third');
  } finally {
    locko.unlock('print');
  }
}

Alternatively, you can use the doWithLock() wrapper function that handles unlocking safely for you:

async function print() {
  await locko.doWithLock('print', async () => {
    console.log('First');
    await wait(100);
    console.log('Second');
    await wait(100);
    console.log('Third');
  });
}