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

rw-resource

v1.0.5

Published

A simple helper to protect access to a resource across async operations

Readme

rw-resource

A simple nodejs helper to protect access to a resource

Description

'rw-resource' is a Node.js module that provides Promises that can be used to protect access to a resource across multiple async operations.

A common use case may be an object that needs to stored to a permanent location regularly but doing so requires multiple async operations, where any modification to that object while the write operations are in progress would prevent storing it successfully.

Examples

import RWRes from 'rw-resource';

/* Create a managed resource (with an initial value) */
let Data = new RWRes({ foo: 'bar' });

/* non-exclusive access */
Data.take()
.then((data) => {
	/* We now have non-exclusive access to the value */
	return delay(250, data)
})
.then((data) => {
	/*
		We are now in a different function, but still have access to the value
		and anyone waiting for exclusive access will not be given the value
		until we leave it.
	*/
	Data.leave();
});

/* Another non-exclusive access */
Data.take()
.then((data) => {
	/*
		We now have non-exclusive access to the value, even though another
		consumer also has non-exclusive access.
	*/
	Data.leave();
});


/* Exclusive access */
Data.take(true)
.then((data) => {
	/*
		We now have exclusive access to the value. The promise will not resolve
		until both of the earlier consumers are done with it.
	*/
	return delay(250, data)
})
.then((data) => {
	Data.leave();
});


/*
	Alternative interface with a self-destructing unlock callback

	Using .lock() returns a promise with a self destructing unlock callback
	instead of the value (which can still be accessed with .value)

	Unlike .leave() which must be called exactly once for each call to .take()
	you may call the unlock callback as many times as you like with no side
	effects.
*/
let unlock;

Data.lock(true)
.then((cb) => {
	unlock = cb;

	return delay(250, Data.value)
})
.then((data) => {
	unlock();

	cnsole.log('Oops, that typo will cause an exception to be thrown');
})
.catch((err) => {
	/* This is safe even if we have already unlocked */
	unlock();
});


/* Helper delay promise */
function delay(time: number, value: any): Promise<any>
{
	return new Promise((resolve, reject) => {
		setTimeout(function() {
			resolve(value);
		}, time);
	});
}