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

shared-exclusive-lock

v0.2.3

Published

Shared read locks and exclusive write locks: Concurrent access for read-only operations, exclusive access for write operations.

Downloads

14

Readme

Shared exclusive lock

NPM package License Build status: Linux and macOS Build status: Windows Coverage status

Shared read locks and exclusive write locks: Concurrent access for read-only operations, exclusive access for write operations.

import Lock from 'shared-exclusive-lock'

const lock = new Lock()

// Multiple read locks at the same time:
const releaseReadLock1 = await lock.readLock()
const releaseReadLock2 = await lock.readLock()

// Write lock is granted as soon as all existing read locks have been released:
lock.writeLock().then((releaseWriteLock) => releaseWriteLock())

// As soon as a write lock is queued, no further read locks are granted in parallel:
lock.readLock().then((releaseReadLock3) => releaseReadLock3())

releaseReadLock1()
releaseReadLock2()

// Sequence:
// 1. Receive first read lock.
// 2. Receive second read lock.
// 3. Release first read lock.
// 4. Release second read lock.
// 5. Receive write lock.
// 6. Release write lock.
// 7. Receive third read lock.
// 8. Release third read lock.

Installation

This is a Node.js module available through the npm registry. You can install the module via the npm install command:

$ npm install shared-exclusive-lock --save

License

Copyright (c) 2017-2018 Sebastian Schmidt

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.