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

individual

v3.0.0

Published

Garantueed individual values

Downloads

4,306,188

Readme

individual

build status Coverage Status Davis Dependency status

NPM

browser support

Garantueed individual values

Example

var Individual = require("individual")

var moduleCache = Individual("__MY_MODULE_CACHE", {})

// moduleCache is a individual variable local to this file.
// It will always be the same value and defaults to {}.

This gives you a singleton value by a unique name (it stores it as a global variable).

Use cases

Your module has an internal cache. If your module is loaded twice, (someone didn't npm dedup and has two copies of your module) you would have two seperate caches that dont talk to each other.

Best case your cache is less efficient. Worst case you have a cache because the native C++ extension you talk to crashes if you instantiate something twice.

You need a garantuee that this value is an individual, there is only one of it.

I use it myself because opening a SockJS websocket to the same URI twice causes an infinite loop. I need a garantuee that I have an individual value for the SockJS connection so I can see whether I already have an open connection.

WHY GLOBALS >:(

I can't imagine any other way to do it. I hate it too. Make a pull request if you know the real solution

Installation

npm install individual

Contributors

  • Raynos

MIT Licenced