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

extrinsic-promises

Package Overview
Dependencies
Maintainers
0
Versions
10
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

extrinsic-promises

A convenient promises anti-pattern: promises you can settle from outside the promise.

  • 3.0.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
3
decreased by-25%
Maintainers
0
Weekly downloads
 
Created
Source

Static Badge JavaScript Standard Style Guide

extrinsic-promises

Supports node versions from v6 up to v22, and 0 runtime dependencies

Deprecated: The functionality provided by this module is now available through the built-in Promise object using the withResolvers function (MDN documentation link). As such, this module is being deprecated and will no longer be maintained. See below for migration patterns.

extrinsic-promises is a JavaScript module that provides a convenient promises anti-pattern for those times when you just really need to settle (fulfill or reject) your promise from outside the promise's work-function.

Specifically, an ExtrinsicPromise is a thennable that you construct without a work-function, and instead call public fulfill and reject methods on the object to settle the state of the promise.

Note: this is generally a promises antipattern. It is not recommended for most use cases, but there are some situations that can't reasonably be handled with traditional promises (at least not without re-implementing extrinsic-promises.)

Migrating from this package to built-in functionality

As of 2023, the JavaScript standard defines a static function called withResolvers on the built-in Promise object. This function provides the same functionality as extrinsic-promises, and should be preferred going forward. The function has widespread browser support and is available by default in NodeJS as of v22. It is also available behind a feature flag as early as Node v21.7.1.

While the interface is not a drop-in replacement, all the functionality is easily supported.

Migration: Creating and settling an externally-settlable promise

Old way:

import ExtrinsicPromise from "extrinsic-promises";

const promise = new ExtrinsicPromise();
promise.fulfill("some value");
promise.reject(new Error("some reason"));

New way:

const { promise, resolve, reject } = Promise.withResolvers();
resolve("some value");
reject(new Error("some reason"));

Migration: adopting a thennable

Old way:

import ExtrinsicPromise from "extrinsic-promises";

const promise = new ExtrinsicPromise();

// ...thennable is a Promise-like object with a then/2 method...
promise.adopt(thennable);

New way:

const { promise, resolve, reject } = Promise.withResolvers();

// ...thennable is a Promise-like object with a then/2 method...
thennable.then(resolve, reject);

Migration: replacing the work method

Old way:

import ExtrinsicPromise from "extrinsic-promises";

const promise = new ExtrinsicPromise();

const myWorkFunction = (fulfill, reject) => {
    // ... do some work and then calls either `fulfill` or `reject`.
};
promise.work(myWork);

New way:

const { promise, resolve, reject } = Promise.withResolvers();

const myWorkFunction = (fulfill, reject) => {
    // ... do some work and then calls either `fulfill` or `reject`.
};
setImmediate(() => {
    try {
        myWorkFunction(resolve, reject);
    } catch (error) {
        reject(error);
    }
});

Or, new way:

const myWorkFunction = (fulfill, reject) => {
    // ... do some work and then calls either `fulfill` or `reject`.
};

const promise = new Promise(myWorkFunction);

Migration: Hiding the Extrinsic methods

Old way:

import ExtrinsicPromise from "extrinsic-promises";

const exPromise = new ExtrinsicPromise();
const p = exPromise.hide();
p.fulfill; // undefined
p.reject; // undefined
p.adopt; // undefined
p.work; // undefined
p.hide; // undefined

When creaeting a promise using withResolvers, there's no need to hide anything, since the "promise" property is already just a plain Promise.

New way:

const { promise: p } = Promise.withResolvers();
p.fulfill; // undefined
p.reject; // undefined
p.adopt; // undefined
p.work; // undefined
p.hide; // undefined
```

## Installation

```console
npm install --save extrinsic-promises

Example

Basic usage:

import ExtrinsicPromise from "extrinsic-promises";

const promise = new ExtrinsicPromise();

// Setup handlers for the promise, just like you normally would.
promise.then(value => {
    console.log("Promise was fulfilled with value:", value);
});

// Call the public methods on the promise to fulfill/resolve it.
promise.fulfill("Some value");

Rejecting a promise:

const promise = new ExtrinsicPromise();

// Register your on-reject handler for the promise,
// just like you normally would.
promise.then(null, reason => {
    console.log("Promise was reject for reason:", reason);
});

// Call the public methods on the promise to reject it.
promise.reject(new Error("some reason"));

Getting an Extended API

The ExtrinsicPromise only provides the basic .then(onFulfill, onReject) method for promises. If you want the convenience methods provided by your favoritate promises library, you can usually use that library to wrap an ExtrinsicPromise appropriately:

import Promise from "bluebird";
import ExtrinsicPromise from "extrinsic-promises";

const exPromise = new ExtrinsicPromise();
const bluebirdPromise = Promise.fulfill(exPromise);

Or, if the library doesn't provide a method like that, you can use the standard Promise constructor as follows:

import ExtrinsicPromise from "extrinsic-promises";

const exPromise = new ExtrinsicPromise();
const otherPromise = new Promise((fulfill, reject) => {
    exPromise.then(fulfill, reject);
});

API

The ExtrinsicPromise class exports the following public methods:

ExtrinsicPromise::then(onFulfill[, onReject])

The standard then method of the Promises/A+ standard, used to register an on-fulfill and/or on-reject handler for the promise.

ExtrinsicPromise::fulfill([withValue])

Resolve (fulfill) the ExtrinsicPromise with the optional given value. Note that there is no gaurantee as to when fulfillment occurs (i.e., synchronously or asynchronously).

This method is already bound and can be used correctly as a function reference. E.g.,:

const exPromise = new ExtrinsicPromise();
const fulfillLater = exPromise.fulfill;
// ...
fulfillLater(value); // correctly fulfills exPromise.

ExtrinsicPromise::reject([forReason])

Reject the ExtrinsicPromise with the optional given reason (typically, an Error object). Note that there is no gaurantee as to when rejection occurs (i.e., synchronously or asynchronously).

This method is already bound and can be used correctly as a function reference. E.g.,:

const exPromise = new ExtrinsicPromise();
const rejectLater = exPromise.reject;
// ...
rejectLater(reason); // correctly rejects exPromise.

ExtrinsicPromise::adopt(thennable)

Adopt the state of the given thennable, once the thennable settles, if this extrinsic promise has not already settled. This is a convenience for using this extrinsic promise's fulfill and reject methods as the on-fulfill and on-reject handlers, respectively, of the given thennable, as follows:

const exPromise = new ExtrinsicPromise();
thennable.then(exPromise.fulfill, exPromise.reject);

ExtrinsicPromise::work(workfunction)

An alternative interface for settling the promise, this allows you to pass in a work-function just like you normally would pass to the Promise constructor, but in this case you're passing it in after the promise has already been constructed.

The given work function will be invoked unconditionally (even if the promise is already settled) with two arguments, typically called fulfill and reject. These are functions that are used to settle the state of the promise once the work you promise to do is done, just like the .fulfill() and .reject() methods on the ExtrinsicPromise.

If an error is thrown inside the workfunction, it will be treated as a rejection.

Note that the work function will be called asynchronously, i.e., the call to .work() will return before the given work function has been called.

ExtrinsicPromise::hide()

Returns a minimal thennable object which only exposes the .then() method of this object as a bound function. This allows you to pass around this object as a promise, without exposing it's state-mutating methods like .fulfill() and .reject().

How Does it Work?

It's pretty simple, feel free to read the code. There's a few details necessary to avoid race conditions, but the gist of it is to simply save the fulfill and reject signalling functions that the promise passes in to the work function:

constructor () {
  new Promise((fulfill, reject) => {
    this.fulfill = fulfill
    this.reject = reject
  })
}

Keywords

FAQs

Package last updated on 08 Jul 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