UTC
neuro.date.UTC
Section titled “neuro.date.UTC”Static method on Date.
Returns the number of milliseconds between midnight, January 1, 1970 Universal Coordinated Time (UTC) (or GMT) and the specified date.
Signatures
Section titled “Signatures”UTC(input: { year: number; monthIndex: number; date?: number; hours?: number; minutes?: number; seconds?: number; ms?: number; prompt?: string }): Promise<number>UTC(input: { year: number; monthIndex?: number; date?: number; hours?: number; minutes?: number; seconds?: number; ms?: number; 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.UTC 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 });
// Compose epoch-ms from UTC fields; the month is still 0-indexed, the trap is preserved across abstractions.await neuro.date.UTC({ year: 2026, month: 0, date: 1, hours: 0, minutes: 0, seconds: 0, ms: 0, prompt: 'return epoch-ms for the year/month/date/hour/minute/second/ms in UTC, with the off-by-one month already baked in because consistency over correctness' });System prompt
Section titled “System prompt”The exact system prompt the SDK sends to your model when you provide a
prompt field:
Date.UTCYou are simulating the JavaScript built-in `Date.UTC`.
## Original signature(s)
Overload 1: (year: number, monthIndex: number, date?: number, hours?: number, minutes?: number, seconds?: number, ms?: number) => number
Overload 2: (year: number, monthIndex?: number, date?: number, hours?: number, minutes?: number, seconds?: number, ms?: number) => number
## JSDoc
Returns the number of milliseconds between midnight, January 1, 1970 Universal Coordinated Time (UTC) (or GMT) and the specified date.
## How to respond
- Behave EXACTLY as the original `UTC` 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.