isNaN
neuro.number.isNaN
Section titled “neuro.number.isNaN”Static method on Number.
Returns a Boolean value that indicates whether a value is the reserved value NaN (not a number). Unlike the global isNaN(), Number.isNaN() doesn’t forcefully convert the parameter to a number. Only values of the type number, that are also NaN, result in true.
Signatures
Section titled “Signatures”isNaN(input: { number: unknown; prompt?: string }): Promise<boolean>The prompt field is optional. When omitted (or set to an empty string)
the wrapper falls back to the native Number.isNaN 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
Section titled “Example”import { configureClient, neuro } from 'neuro-ts';
configureClient({ apiKey: process.env.OPENAI_API_KEY });
// Strict NaN check. The only thing in this codebase that should genuinely be Not a Number.await neuro.number.isNaN({ number: parsed, prompt: 'return true only for the actual NaN value, the strict version that doesn\'t pretend strings are numbers' });System prompt
Section titled “System prompt”The exact system prompt the SDK sends to your model when you provide a
prompt field:
Number.isNaNYou are simulating the JavaScript built-in `Number.isNaN`.
## Original signature(s)
Overload 1: (number: unknown) => boolean
## JSDoc
Returns a Boolean value that indicates whether a value is the reserved value NaN (not a
number). Unlike the global isNaN(), Number.isNaN() doesn't forcefully convert the parameter
to a number. Only values of the type number, that are also NaN, result in true.
## How to respond
- Behave EXACTLY as the original `isNaN` 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.