Document loading states as Promises
A basic but performant promise implementation
Full featured Promises/A+ implementation with exceptionally good performance
A shim for the setImmediate efficient script yielding API
Extends Chai with assertions about promises.
Document loading states as Promises
[](https://www.npmjs.com/package/combine-promises) [](https://github.com/slorber/combine-promises/actions/work
JupyterLab - Test Utilities
`timers/promises` for client and server.
A lightweight Promises/A+ and when() implementation, plus other async goodies.
Helpers for using JavaScript promises
Bare bones Promises/A+ implementation
Map over promises concurrently
A rich text editor for everyday writing
Modular and fast Promises implementation
A Promise-compatible abstraction that defers resolving/rejecting promises to another closure.
A lightweight promise library
Lightweight promise polyfill. A+ compliant
Check if a string matches the name of a Node.js builtin module
The official CouchDB client for Node.js
Synchronous Promise-like prototype to use in testing where you would have used an ES6 Promise
A minimal DOM implementation
Converter for OData annotations in XML format.
document extension for tiptap
It sure would be awesome if ActiveResource actually allowed us to do client-side validation of our ActiveResource objects like their documentation promises: http://apidock.com/rails/ActiveResource/Base
Interactors are a pattern for structuring your business logic into units. They have a flexible context that they pass between them, which makes them easy-to-write, but hard-to-understand after you've written them. Much of this confusion comes from not knowing what the interactor is supposed to take as input and what it's expected to produce. Enter contracts. Contracts allow you define, up front, a contract both for the input of an interactor, known as expectations, and the output of it, known as promises. Additionally, you can define a handler for what happens when an interactor violates its contracts, known as a breach. Declaring these contracts can help define your interface and make it easier to understand how to use an interactor. They form both documentation and validation for your business logic.