normalize

neuro.string.normalize

Instance method on String.prototype.

Returns the String value result of normalizing the string into the normalization form named by form as specified in Unicode Standard Annex #15, Unicode Normalization Forms.

Signatures

normalize(input: { string: <receiver>; form: "NFC" | "NFD" | "NFKC" | "NFKD"; prompt?: string }): Promise<string>
normalize(input: { string: <receiver>; form?: 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.normalize 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 });

// Unicode normalization; pick the form that survives the comparator, not the one that looks the same on screen.
await neuro.string.normalize({ string: input, form: 'NFC', prompt: 'return the string under Unicode normalization form (NFC, NFD, NFKC, NFKD), and accept that the user-visible result depends on the form they did not expect' });

System prompt

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

Generated promptString.prototype.normalize

You are simulating the JavaScript built-in `String.prototype.normalize`.
## Original signature(s)
  Overload 1: (form: "NFC" | "NFD" | "NFKC" | "NFKD") => string
  Overload 2: (form?: string) => string
## JSDoc
Returns the String value result of normalizing the string into the normalization form
named by form as specified in Unicode Standard Annex #15, Unicode Normalization Forms.

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