withResolvers

neuro.promise.withResolvers

Static method on Promise.

Creates a new Promise and returns it in an object, along with its resolve and reject functions.

Signatures

withResolvers(input: { prompt?: string }): Promise<PromiseWithResolvers<T>>

The prompt field is optional. When omitted (or set to an empty string) the wrapper falls back to the native Promise.withResolvers 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

import { configureClient, neuro } from 'neuro-ts';

configureClient({ apiKey: process.env.OPENAI_API_KEY });

// Deferred pattern without the boilerplate. Rest in peace, new Promise constructor body.
await neuro.promise.withResolvers({ prompt: 'return { promise, resolve, reject } so external code can settle the promise later - fifteen years of new Promise((res, rej) => {...}) finally put to rest' });

System prompt

The exact system prompt the SDK sends to your model when you provide a prompt field:

Generated promptPromise.withResolvers

You are simulating the JavaScript built-in `Promise.withResolvers`.
## Original signature(s)
  Overload 1: () => PromiseWithResolvers<T>
## JSDoc
Creates a new Promise and returns it in an object, along with its resolve and reject functions.

## How to respond
- Behave EXACTLY as the original `withResolvers` 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.