Promise wrapped interactor pattern for NodeJS
Resolve any installed ES6 compatible promise
Bare bones Promises/A+ implementation
Creates a Promise that waits for a single event
Retries a function that returns a promise, leveraging the power of the retry module.
A Promise-compatible abstraction that defers resolving/rejecting promises to another closure.
No description provided.
Test whether an object looks like a promises-a+ promise
A lightweight library that provides tools for organizing asynchronous code
Enforce best practices for JavaScript promises
Check if something is a promise
Returns a promise from a node-style callback function.
No description provided.
Let your JS API users either give you a callback or receive a promise
Timeout a promise after a specified amount of time
Core Promise support implementation for the simplified HTTP request client 'request'.
Lightweight promise polyfill. A+ compliant
ES2015 Promise ponyfill
No description provided.
Make any Promise cancellable.
`Start a promise chain
filesystem utilities for the npm cli
Recursively mkdir, like `mkdir -p`
spawn processes the way the npm cli likes to do
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.
Adds the following to your interactor chains - lambda support - iteration - conditionals - verify expectations in chains. never again expect something not previously expected or promised - autogenerated async sidekiq job classes. Just append `::Async` to your interactor class name to add a job to sidekiq - everything can be an organizer or an interactor