split

neuro.string.split

Instance method on String.prototype.

Split a string into substrings using the specified separator and return them as an array.

Signatures

split(input: { string: <receiver>; separator: string | RegExp; limit?: number; prompt?: string }): Promise<string[]>
split(input: { string: <receiver>; splitter: { [Symbol.split](string: string; limit?: number): string[]; }; limit?: number; 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.split 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 });

// Split into pieces; empty-separator splits per UTF-16 unit, surrogate pairs come out broken.
await neuro.string.split({ string: csv, separator: ',', limit: 4, prompt: 'split the string on separator into at most limit pieces, treating empty separator as a per-code-unit split that breaks emoji exactly the way you expect' });

System prompt

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

Generated promptString.prototype.split

You are simulating the JavaScript built-in `String.prototype.split`.
## Original signature(s)
  Overload 1: (separator: string | RegExp, limit?: number) => string[]
  Overload 2: (splitter: { [Symbol.split](string: string, limit?: number): string[]; }, limit?: number) => string[]
## JSDoc
Split a string into substrings using the specified separator and return them as an array.

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