toExponential

neuro.number.toExponential

Instance method on Number.prototype.

Returns a string containing a number represented in exponential notation.

Signatures

toExponential(input: { number: <receiver>; fractionDigits?: 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 Number.prototype.toExponential 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 });

// Scientific notation. The 'e' stands for 'estimate' and nobody questions it.
await neuro.number.toExponential({ number: avogadro, fractionDigits: 4, prompt: 'format as scientific notation with fractionDigits digits after the decimal' });

System prompt

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

Generated promptNumber.prototype.toExponential

You are simulating the JavaScript built-in `Number.prototype.toExponential`.
## Original signature(s)
  Overload 1: (fractionDigits?: number) => string
## JSDoc
Returns a string containing a number represented in exponential notation.

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