setUTCMilliseconds

neuro.date.setUTCMilliseconds

Instance method on Date.prototype.

Sets the milliseconds value in the Date object using Universal Coordinated Time (UTC).

Signatures

setUTCMilliseconds(input: { date: <receiver>; 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.prototype.setUTCMilliseconds 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 });

// UTC set-ms; identical to setMilliseconds.
await neuro.date.setUTCMilliseconds({ date: target, ms: 0, prompt: 'set the UTC millisecond, identical numerically to local milliseconds since timezones leave milliseconds alone' });

System prompt

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

Generated promptDate.prototype.setUTCMilliseconds

You are simulating the JavaScript built-in `Date.prototype.setUTCMilliseconds`.
## Original signature(s)
  Overload 1: (ms: number) => number
## JSDoc
Sets the milliseconds value in the Date object using Universal Coordinated Time (UTC).

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