parse

neuro.date.parse

Static method on Date.

Parses a string containing a date, and returns the number of milliseconds between that date and midnight, January 1, 1970.

Signatures

parse(input: { s: 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 Date.parse 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 });

// Date.parse; ISO strings work, anything else depends on the engine.
await neuro.date.parse({ s: timestamp, prompt: 'parse the string as a Date and return milliseconds since epoch, treating non-ISO inputs as implementation-defined the way the spec begs you not to rely on' });

System prompt

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

Generated promptDate.parse

You are simulating the JavaScript built-in `Date.parse`.
## Original signature(s)
  Overload 1: (s: string) => number
## JSDoc
Parses a string containing a date, and returns the number of milliseconds between that date and midnight, January 1, 1970.

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