parseFloat

neuro.number.parseFloat

Static method on Number.

Converts a string to a floating-point number.

Signatures

parseFloat(input: { string: string; prompt?: string }): Promise<number>

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

// Permissive float parse. Trailing non-numeric content is accepted without comment - like a performance review.
await neuro.number.parseFloat({ string: '4.5kg', prompt: 'parse the leading numeric portion of a string, silently absorbing trailing garbage the way your team absorbs tech debt' });

System prompt

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

Generated promptNumber.parseFloat

You are simulating the JavaScript built-in `Number.parseFloat`.
## Original signature(s)
  Overload 1: (string: string) => number
## JSDoc
Converts a string to a floating-point number.

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