Research
Security News
Quasar RAT Disguised as an npm Package for Detecting Vulnerabilities in Ethereum Smart Contracts
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
async-later
Advanced tools
Return a Promise
or an AsyncIterable
now and handle the logic later! Use in conjunction with the amazing streaming-iterables
package and write elegant functional code.
There are no dependencies.
npm i --save async-later
We ship esm and types.
resolveLater()
iterateLater()
partition()
toAsyncIterable()
firstValue()
lastValue()
valueAt()
concurrently()
function resolveLater<T>(): [Promise<T>, Resolve<T>]
// type Resolve<T> = (value?: T | PromiseLike<T>) => void;
Creates a Promise
and passes its resolve
to the outer scope (in the native Promise API, resolve
is only accessible through new Promise((resolve, reject) => {...})
).
import { resolveLater } from 'async-later';
const [value, setValue] = resolveLater();
value.then(console.log);
setValue(42);
// 42
Real world example adapted from @functionland/protocols/file:
// Customizable backend for "save"
type SaveMethod = (blog: Blog, declareId: (id: string) => void) => any;
// We want to pass a callback, "declareId", to custom implementations
// to be invoked with "id" when they are done
let saveMethod: SaveMethod = async () => {}; // Default: no implementation
export function changeSaveMethod(method: SaveMethod) {
saveMethod = method;
}
export function save(blog: Blog): Promise<string> { // returns Promise of saved blog's id
const [id, resolve] = resolveLater<string>();
saveMethod(blog, resolve);
return id;
}
function iterateLater<T>(): [AsyncIterable<T>, Resolve<T>, () => void]
Creates next()
and complete()
interfaces for an AsyncIterable
(similar to Observable
s). Stalls on back pressure and caches when read is slower.
import { iterateLater } from 'async-later';
const [iterable, next, complete] = iterateLater();
next(1);
next(2);
next(3);
complete();
for await (const value of iterable) {
console.log(value);
}
// 1
// 2
// 3
function partition<T>(index: number, iterable: AsyncIterable<T>): [AsyncIterable<T>, AsyncIterable<T>]
Decomposes an AsyncIterable
into two at an index
(more partitions can be made by subsequent/recursive calls).
import { partition, toAsyncIterable } from 'async-later';
const [p1, rest] = partition(2, toAsyncIterable([1, 2, 3, 4, 5]));
const [p2, p3] = partition(2, rest);
for await (const value of p1) {
console.log(value);
}
// 1
// 2
for await (const value of p2) {
console.log(value);
}
// 3
// 4
for await (const value of p3) {
console.log(value);
}
// 5
function toAsyncIterable<T>(
value: T | PromiseLike<T> | ObservableLike<T> | Iterable<PromiseLike<T> | T> | AsyncIterable<T>
): AsyncIterable<T>
// Curried overload suitable for pipeline:
export function toAsyncIterable<T>(): (
value: T | PromiseLike<T> | ObservableLike<T> | Iterable<PromiseLike<T> | T> | AsyncIterable<T>
) => AsyncIterable<T>
Converts anything to an AsyncIterable
!
import { toAsyncIterable } from 'async-later';
for await (const value of toAsyncIterable(42)) {
console.log(value);
}
// 42
for await (const value of toAsyncIterable(Promise.resolve(42))) {
console.log(value);
}
// 42
for await (const value of toAsyncIterable([42])) {
console.log(value);
}
// 42
for await (const value of toAsyncIterable([])) {
console.log(value); // Will not execute
}
for await (const value of toAsyncIterable([1, 2, 3])) {
console.log(value);
}
// 1
// 2
// 3
for await (const value of toAsyncIterable([1, Promise.resolve(2), Promise.resolve(3)])) {
console.log(value);
}
// 1
// 2
// 3
function firstValue<T>(iterable: Iterable<T> | AsyncIterable<T>): Promise<T>
// Curried overload suitable for pipeline:
function firstValue<T>(): (iterable: Iterable<T> | AsyncIterable<T>) => Promise<T>
Returns the first value from an AsyncIterable
as a Promise
. The Promise
rejects if iterable is empty.
import { firstValue, toAsyncIterable } from 'async-later';
const iterable = toAsyncIterable([1, 2, 3]);
console.log(await firstValue(iterable));
// 1
function lastValue<T>(iterable: Iterable<T> | AsyncIterable<T>): Promise<T>
// Curried overload suitable for pipeline:
function lastValue<T>(): (iterable: Iterable<T> | AsyncIterable<T>) => Promise<T>
Returns the last value from an AsyncIterable
as a Promise
. The Promise
rejects if iterable is empty.
import { lastValue, toAsyncIterable } from 'async-later';
const iterable = toAsyncIterable([1, 2, 3]);
console.log(await lastValue(iterable));
// 3
function valueAt<T>(index: number, iterable: Iterable<T> | AsyncIterable<T>): Promise<T>
// Curried overload suitable for pipeline:
function valueAt<T>(index: number): (iterable: Iterable<T> | AsyncIterable<T>) => T
Returns the value specified by an index
in an AsyncIterable
, as a Promise
. The Promise
rejects if iterable is empty or index
>= length.
import { valueAt, toAsyncIterable } from 'async-later';
const iterable = toAsyncIterable([1, 2, 3]);
console.log(await valueAt(1, iterable));
// 2
function concurrently<T>(...functions: (() => T | PromiseLike<T>)[]): Promise<T[]>
Invokes functions
with Promise.all
.
import { concurrently } from 'async-later';
const result = await concurrently(
() => 42,
() => Promise.resolve(42),
async () => 42,
() => 24,
async () => 24
);
console.log(result)
// [42, 42, 42, 24, 24]
FAQs
Functional directives for Promise and AsyncIterable
We found that async-later demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
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.
Research
Security News
Socket researchers uncover a malicious npm package posing as a tool for detecting vulnerabilities in Etherium smart contracts.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.