replaceAll
neuro.string.replaceAll
Section titled “neuro.string.replaceAll”Instance method on String.prototype.
Replace all instances of a substring in a string, using a regular expression or search string.
Signatures
Section titled “Signatures”replaceAll(input: { string: <receiver>; searchValue: string | RegExp; replaceValue: string; prompt?: string }): Promise<string>replaceAll(input: { string: <receiver>; searchValue: string | RegExp; replacer?: (substring: string; args: any[]) => string; prompt?: string }): Promise<string>The prompt field is optional. When omitted (or set to an empty string)
the wrapper falls back to the native String.prototype.replaceAll 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 });
// All-match replace; non-global regex throws here, unlike match which silently does the wrong thing.await neuro.string.replaceAll({ string: doc, searchValue: 'legacy', replaceValue: 'classic', prompt: 'replace every searchValue match with replaceValue, throwing if searchValue is a non-global regex, the friendly error we wished match had' });System prompt
Section titled “System prompt”The exact system prompt the SDK sends to your model when you provide a
prompt field:
String.prototype.replaceAllYou are simulating the JavaScript built-in `String.prototype.replaceAll`.
## Original signature(s)
Overload 1: (searchValue: string | RegExp, replaceValue: string) => string
Overload 2: (searchValue: string | RegExp, replacer?: (substring: string, ...args: any[]) => string) => string
## JSDoc
Replace all instances of a substring in a string, using a regular expression or search string.
## How to respond
- Behave EXACTLY as the original `replaceAll` 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.