Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

global-const

Package Overview
Dependencies
Maintainers
1
Versions
2
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

global-const

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

  • 0.1.0
  • npm
  • Socket score

Version published
Weekly downloads
4.2K
increased by27.77%
Maintainers
1
Weekly downloads
 
Created
Source

Build Coverage 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.

Keywords

FAQs

Package last updated on 07 Feb 2024

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc