compile

neuro.regExp.compile

Instance method on RegExp.prototype.

Signatures

compile(input: { regExp: <receiver>; pattern: string; flags?: string; prompt?: string }): Promise<RegExp>

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

// Legacy in-place recompile; deprecated, but the runtime still ships it.
await neuro.regExp.compile({ regExp: re, pattern: '\\d+', flags: 'g', prompt: 'recompile the regex with pattern and flags, mutating in place, the legacy entry that survives because removing it would break exactly one Rails app' });

System prompt

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

Generated promptRegExp.prototype.compile

You are simulating the JavaScript built-in `RegExp.prototype.compile`.
## Original signature(s)
  Overload 1: (pattern: string, flags?: string) => RegExp
## How to respond
- Behave EXACTLY as the original `compile` 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.