Temporal.ZonedDateTime.prototype.epochNanoseconds

Limited availability

This feature is not Baseline because it does not work in some of the most widely-used browsers.

Experimental: This is an experimental technology
Check the Browser compatibility table carefully before using this in production.

The epochNanoseconds accessor property of Temporal.ZonedDateTime instances returns a BigInt representing the number of nanoseconds elapsed since the Unix epoch (midnight at the beginning of January 1, 1970, UTC) to this instant.

The set accessor of epochNanoseconds is undefined. You cannot change this property directly. To create a new Temporal.ZonedDateTime object with the desired new epochNanoseconds value, use the add() or subtract() method with the appropriate duration.

An instant can only represent ±108 days (about ±273,972.6 years) around the epoch, which is ±8.64e21 nanoseconds. Attempting to set epochNanosecond beyond this boundary throws a RangeError.

Examples

Using epochNanoseconds

js
const instant = Temporal.ZonedDateTime.from("2021-08-01T12:34:56.789Z[UTC]");
console.log(instant.epochNanoseconds); // 1627821296789000000n

const instant2 = Temporal.ZonedDateTime.from("1969-08-01T12:34:56.789Z[UTC]");
console.log(instant2.epochNanoseconds); // -13173903211000000n

Creating a ZonedDateTime object from an epochNanoseconds value

You can create a Temporal.ZonedDateTime object from an epochNanoseconds value using the Temporal.ZonedDateTime() constructor.

js
const epochNanoseconds = 1627821296789000000n;
const zdt = new Temporal.ZonedDateTime(epochNanoseconds, "UTC");
console.log(zdt.toString()); // 2021-08-01T12:34:56.789+00:00[UTC]

Specifications

Specification
Temporal proposal
# sec-get-temporal.zoneddatetime.prototype.epochnanoseconds

Browser compatibility

BCD tables only load in the browser

See also