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

cross-process-lock

v2.1.1

Published

Cross-process file locking solution with lock-queue

Downloads

33,450

Readme

cross-process-lock

Downloads Version@npm Version@git CI Docs

Cross-process file locking solution with lock-queue

Usage

const { lock } = require('cross-process-lock');
const { writeFileSync } = require('fs');
// create a lock for the given file
const unlock = await lock('file.txt')
// do smth with the file here
writeFileSync('file.txt', 'some content', 'utf8');
// unlock file with the received function
return unlock();

API

Lock

lock(file[, options]) - creates a lock for the given file for the actual process

Arguments:

  • {string} file - the path of the file needs to be locked
  • {lockOptions} options - the options to use to lock file, e.g timeouts

Returns: Promise<Function> - resolved with unlock function in case of successful lock; rejected in case of file couldn't be lock in the given timeout

Unlock

unlock(file) - deletes the lock for the given file for the actual process

Arguments:

  • {string} file - the path of the file needs to be unlocked

Returns: Promise - resolved in case of successful unlock or rejected in case of any error

WithLock

withLock(file[, options], callback) - executes the callback with locking before and unlocking after the execution

Arguments:

  • {string} file - path of the file needs to be locked
  • {lockOptions} options - the options to use to lock file, e.g timeouts
  • {() => Promise<T>} callback - the function to be executed

Returns: Promise<T> - resolved/rejected with the result of the callback

lockOptions

| Option | Description | Default | | :--------------------- | :--------------------------------------------- | :--------: | | lockTimeout {number} | timeout (ms) when locks automatically released | 20 minutes | | waitTimeout {number} | timeout (ms) until lock waits to lock a file | 10 seconds |

Debug

The package uses the debug NPM package with cross-process-lock:PID name, where PID is the process ID of the current process.

To enable debug logging, use for example the DEBUG=cross-process-lock:* environment variable, but for more information, check the documentation of the debug package.