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

@sosimple/fsx-lockfile

v0.3.0

Published

A library which allows multiple concurrent processes to safely update shared files.

Readme

Lock File

A lock file library which allows multiple concurrent processes to safely update shared files.

Path requirements

This package intentionally does not resolve symbolic links. Every process must use the same canonical target path for all lockfile operations and ordinary file access. The target path and the path produced by lockName must not contain symbolic links.

When an input path may contain symbolic links, call canonicalPath from @sosimple/fsx once, then reuse the resulting path or File for lock(), isLocked(), forceUnlock(), and withLock():

import { canonicalPath } from "@sosimple/fsx";
import { File } from "@sosimple/fsx-file";
import { LockFile } from "@sosimple/fsx-lockfile";

const file = new File(await canonicalPath(inputPath));

await LockFile.withLock(file, options, async (lock) => {
  // Read through file and stage updates through lock.
});

The caller must also ensure that custom lock directories used by lockName do not contain symbolic links. Hard links, bind mounts, filesystem case aliases, and concurrent changes to the path hierarchy can still give one filesystem entry multiple identities. Using such aliases, changing the selected path, or passing paths containing unresolved symbolic links results in undefined behavior and can break mutual exclusion or modify the wrong filesystem entry.