any
neuro.promise.any
Section titled “neuro.promise.any”Static method on Promise.
The any function returns a promise that is fulfilled by the first given promise to be fulfilled, or rejected with an AggregateError containing an array of rejection reasons if all of the given promises are rejected. It resolves all elements of the passed iterable to promises as it runs this algorithm.
Signatures
Section titled “Signatures”any(input: { values: T; prompt?: string }): Promise<Promise<Awaited<T[number]>>>any(input: { values: Iterable<T | PromiseLike<T>>; prompt?: string }): Promise<Promise<Awaited<T>>>The prompt field is optional. When omitted (or set to an empty string)
the wrapper falls back to the native Promise.any and returns a
resolved Promise without contacting the LLM. When present, the LLM is given
the original arguments plus your prompt and is asked to behave like the
original method.
Example
Section titled “Example”import { configureClient, neuro } from 'neuro-ts';
configureClient({ apiKey: process.env.OPENAI_API_KEY });
// First-success. AggregateError on total failure carries every rejection. Thoroughly.await neuro.promise.any({ values: replicas, prompt: 'resolve to the first promise that fulfills, reject with an AggregateError only when every single one rejects, carrying everyone\'s excuses' });System prompt
Section titled “System prompt”The exact system prompt the SDK sends to your model when you provide a
prompt field:
Promise.anyYou are simulating the JavaScript built-in `Promise.any`.
## Original signature(s)
Overload 1: (values: T) => Promise<Awaited<T[number]>>
Overload 2: (values: Iterable<T | PromiseLike<T>>) => Promise<Awaited<T>>
## JSDoc
The any function returns a promise that is fulfilled by the first given promise to be fulfilled, or rejected with an AggregateError containing an array of rejection reasons if all of the given promises are rejected. It resolves all elements of the passed iterable to promises as it runs this algorithm.
## How to respond
- Behave EXACTLY as the original `any` would, but use the user's intent to choose any callback / comparator / transform logic that the original would normally accept as an argument.
- Strictly preserve the original return type and shape.
- Output ONLY the JSON-encoded return value of the function call.
- Do NOT include explanations, prose, comments, or markdown fences.
- If the function would return `undefined`, output the literal string `undefined`.
- For Date / RegExp / Map / Set / TypedArray returns, output an object of the form { "__type": "Date" | "RegExp" | "Map" | "Set" | "<TypedArrayName>", ... } so the SDK can rehydrate it.