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

global-const

v0.1.2

Published

A lightweight utility to create global singletons (on browser and node)

Downloads

6,270

Readme

BuildCoverage Status

A lightweight utility to create global singletons (on browser and node)

[!WARNING] Attaching items on globals should be a last resort, so only do this if you must... But sometimes you've got to do what you've got to do, and for that, this package exists.

Basic features

  • Works in Node and the browser
  • Namespace in global object to prevent collision if multiple projects use this.
  • Globally reference any kind of variable, object/function
  • TypeScript support

Installation

To install global-const, use npm or yarn as follows:

npm install global-const
# or
yarn add global-const

Usage

import { getGlobalisedValue, clearGlobalNamespace } from "global-const";

const targetFunction = (someParams) => {
  // some function that maintains state, or works
  // within a closure.
};

const singletonInstance = getGlobalisedValue(
  "namespace",
  "targetFunction",
  targetFunction
);

// ...
singletonInstance("...");

// ... somewhere else in code

// this will get the same function instance as above
const anotherInstance = getGlobalisedValue(
  "namespace",
  "targetFunction",
  targetFunction
);

expect(singletonInstance).toBe(anotherInstance); // true

Why would you need this library?

While it's generally not advised to add code to the global-state (window/globalThis), you might need to. This library comes handle to manage this.

And example is when you have many packages, each using a "metrics" module. When a customer individually instantiates each module, each module will probably instantiate it's own metrics tracking module. However if you wish for all the features to use the same metrics tracking function, instead of being siloed, this feature will help ensure that each time the metrics functions are instantiated, they'll check if there's one that's been globalised, and if so return that one instead.

[!CAUTION] This assumes that each instantiation is the same as the other, so be careful to ensure that your customers aren't likely to mix different versions of the function.

API Reference

getGlobalisedValue(namespace, key, value)

  • namespace: A unique string identifier to prevent collisions when considering other packages using this module.
  • key: The name of the value to retrieve or set.
  • value: An object/function to be globalised if it doesn't already exist.

Returns the globalised value or stores the value passed in if not initialised, and returns it.

const logger = getGlobalisedValue("myApp", "logger", new Logger());

clearGlobalNamespace(namespace)

  • namespace: A unique string identifier to prevent collisions when considering other packages using this module.

This function is used for an application to clear out it's namespace.