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

@nexfteam/single-instance

v0.0.8

Published

Check if an instance of the current application is running or not.

Readme

node-single-instance

This package intends to make it easier to have a single instance of an application running.

While the few other packages with the same purpose are either complicated (need a database) or doing the check only on Windows, single-instance try to be easy to use and for all platform.

  • Why all platforms ?

    It is true that on OSX for example you doesn't need this check but you might want to do something in case someone try to run the application a second time (like focusing the running app for example).

Usage

  • Install it:
npm install @nexfteam/single-instance
  • Use it !
import { SingleInstance } from "@nexfteam/single-instance";

const locker = new SingleInstance("my-app-name", {
  // This option is optional
  // You can customize the socket path
  // socketPath: '/tmp/my-app-name.sock',
  userSpecific: true,
  // If you want not to use user specific socket path, set this to false(Default is true)
});

try {
  await locker.lock();
  // We just locked our application,
  // now we can do what we want !
  // You can also pass data to the locker:
  // await locker.lock(JSON.stringify(process.argv));
} catch (err) {
  // Quit the application
  process.exit(0);
}

locker.on("connection-attempt", (data) => {
  // When other instances try to connect, you can do something here,
  // like focusing the running app for example.
  console.log(data);
  // If the connection has data, you can get it in the event data.
  // If the connection has no data, data will be null.
});

Support

License

MIT