Running cookbook files: see instructions in ../polyfill/README.md
These are some of the most common tasks that people ask questions about on StackOverflow with legacy Date
.
Here's how they would look using Temporal
.
How to get the current date and time in the local time zone?
{{cookbook/getCurrentDate.mjs}}
Note that if you just want the date and not the time, you should use Temporal.PlainDate
.
If you want both, use Temporal.PlainDateTime
.
How to get a Unix timestamp?
{{cookbook/getTimeStamp.mjs}}
Here's how to convert legacy ECMAScript Date
into a Temporal.Instant
or Temporal.ZonedDateTime
instance corresponding to the same instant in exact time.
{{cookbook/fromLegacyDate.mjs}}
A common bug arises from a simple question: what date (year, month, and day) is represented by this Date
?
The problem: the answer depends on the time zone.
The same Date
can be December 31 in San Francisco but January 1 in London or Tokyo.
Therefore, it's critical to interpret the Date
in context of the correct time zone before trying to extract the year, month, or day, or before doing calculations like "did this happen yesterday?" involving date units.
For this reason, Temporal.Instant
(which is the Temporal
equivalent of Date
) does not have year
, month
, day
properties.
To access date or time units in Temporal
, a time zone must be provided, as described in the code example above.
Another bug-prone case is when Date
is (ab)used to store a date-only value, like a user's date of birth.
With Date
these values are typically stored with midnight times, but to read back the date correctly you need to know which time zone's midnight was used to create the Date
.
For example, new Date(2000, 0, 1)
uses the caller's time zone, while new Date('2000-01-01')
uses UTC.
To correctly convert a date-only Date
to a Temporal.PlainDate
without being vulnerable to off-by-one-day bugs, you must determine which time zone's midnight was used to construct the Date
, and then use that same time zone when converting from Temporal.Instant
to Temporal.PlainDate
.
{{cookbook/fromLegacyDateOnly.mjs}}
Legacy Date
represents an exact time, so it's straightforward to convert a Temporal.Instant
or Temporal.ZonedDateTime
instance into a legacy Date
instance that corresponds to it.
{{cookbook/toLegacyDate.mjs}}
Temporal.TimeZone.from()
can convert an IANA time zone name into a Temporal.TimeZone
object, if you need to call Temporal.TimeZone
methods.
Usually this is not necessary.
{{cookbook/getTimeZoneObjectFromIanaName.mjs}}
You can use Temporal
objects to set properties on a calendar control.
Here is an example using an HTML <input type="date">
element with any day beyond “today” disabled and not selectable.
{{cookbook/calendarInput.js}}
An example of combining a calendar date (Temporal.PlainDate
) and a wall-clock time (Temporal.PlainTime
) into a Temporal.PlainDateTime
.
{{cookbook/noonOnDate.mjs}}
An example of combining a day on the calendar (Temporal.PlainMonthDay
) and a year into a Temporal.PlainDate
.
{{cookbook/birthdayIn2030.mjs}}
To serialize an exact-time Temporal.Instant
into a string, use toString()
.
Without any arguments, this gives you a string in UTC time.
If you need your string to include a UTC offset, then use the timeZone
option of Temporal.Instant.prototype.toString()
which will return a string serialization of the wall-clock time in that time zone corresponding to the exact time.
This loses the information about which time zone the string was in, because it only preserves the UTC offset from the time zone at that particular exact time.
If you need your string to include the time zone name, use Temporal.ZonedDateTime
instead, which retains this information.
{{cookbook/getParseableZonedStringAtInstant.mjs}}
Each Temporal
type has a compare()
static method, which can be passed to Array.prototype.sort()
as the compare function in order to sort an array of Temporal
types.
Sort a list of Temporal.PlainDateTime
s, for example in order to get a conference schedule in the correct order.
Sorting other Temporal
types would work exactly the same way.
{{cookbook/getSortedLocalDateTimes.mjs}}
Sort a list of ISO 8601 date/time strings, for example to place log entries in order.
{{cookbook/sortExactTimeStrings.mjs}}
Use the round()
method of each Temporal
type if you want to round the time fields.
Here's an example of rounding a time down to the previously occurring whole hour:
{{cookbook/roundDownToWholeHours.mjs}}
Rounding is only defined for time fields.
Rounding a date field can be ambiguous, so date-only types such as Temporal.PlainDate
don't have a round()
method.
If you need to round a date to the nearest month, for example, then you must explicitly pick what kind of rounding you want.
Here is an example of rounding to the nearest start of a month, rounding up in case of a tie:
{{cookbook/roundToNearestMonth.mjs}}
See also Push back a launch date for an easier way to round up unconditionally to the next start of a month.
Map a zoneless date and time of day into a Temporal.Instant
instance at which the local date and time of day in a specified time zone matches it.
This is easily done with dateTime.toZonedDateTime(timeZone).toInstant()
, but here is an example of implementing different disambiguation behaviors than the 'compatible'
, 'earlier'
, 'later'
, and 'reject'
ones built in to Temporal
.
{{cookbook/getInstantWithLocalTimeInZone.mjs}}
Map a zoned date and time of day into another zoned date and time of day in a target time zone at the corresponding exact time. This could be used when converting user-input date-time values between time zones.
{{cookbook/zonedDateTimeInOtherZone.mjs}}
Here is another example similar to the previous one, using the time zone for future events. The times and locations of a series of future meetings are stored as a pair of strings: one for the calendar date and wall-clock time, and one for the time zone. They cannot be stored as an exact time because between now and the time when the event happens, the time zone rules for daylight saving time could change — for example, Brazil abolished daylight saving time in 2019 — but the meeting would still be held at the same wall-clock time on that date. So if the time zone rules changed, the event's exact time would change.
This example calculates the starting times of all the Ecma TC39 meetings in 2019, in local time in Tokyo.
{{cookbook/localTimeForFutureEvents.mjs}}
Similar to the previous recipe, calculate the exact times of a daily occurrence that happens at a particular local time in a particular time zone.
{{cookbook/calculateDailyOccurrence.mjs}}
Use Temporal.TimeZone.getOffsetStringFor()
or Temporal.ZonedDateTime.offset
to map a Temporal.Instant
instance and a time zone into the UTC offset at that exact time in that time zone, as a string.
{{cookbook/getUtcOffsetStringAtInstant.mjs}}
Similarly, use Temporal.TimeZone.getOffsetNanosecondsFor()
to do the same thing for the offset as a number of seconds.
(Remember to divide by 109 to convert nanoseconds to seconds.)
{{cookbook/getUtcOffsetSecondsAtInstant.mjs}}
Also using Temporal.TimeZone.getOffsetNanosecondsFor()
, we can map a Temporal.Instant
instance and two time zones into the signed difference of UTC offsets between those time zones at that exact time, as a number of seconds.
{{cookbook/getUtcOffsetDifferenceSecondsAtInstant.mjs}}
Here is an example of Temporal
used in a graph, showing fictitious activity for a storage tank in a fixed location (Stockholm, Sweden).
The graph always starts at midnight in the tank's location, but the graph labels are in the viewer's time zone.
{{cookbook/storageTank.js}}
Across the web there are several tools for finding meeting times that are appropriate for all the participants' time zones, such as World Time Buddy, World Clock Meeting Planner, and built into various calendar software.
<style> #meeting-planner { border-collapse: separate; border-spacing: 0 10px; font-size: 0.6rem; text-align: center; } /* https://materializecss.com/color.html */ .time-0, .time-1, .time-2, .time-3, .time-4, .time-5, .time-22, .time-23 { background-color: #ef9a9a; /* red lighten-3 */ border-color: #e57373; /* red lighten-2 */ border-style: solid; border-width: 0 1px; } .time-6, .time-7, .time-18, .time-19, .time-20, .time-21 { background-color: #fff59d; /* yellow lighten-3 */ border-color: #ffd54f; /* amber lighten-2 */ border-style: solid; border-width: 0 1px; } .time-8, .time-9, .time-10, .time-11, .time-12, .time-13, .time-14, .time-15, .time-16, .time-17 { background-color: #a5d6a7; /* green lighten-3 */ border-color: #81c784; /* green lighten-2 */ border-style: solid; border-width: 0 1px; } .time-0 { border-bottom-left-radius: 12px; border-left-color: white; border-left-width: 2px; border-top-left-radius: 12px; font-weight: bold; } .time-23 { border-bottom-right-radius: 12px; border-right-color: white; border-right-width: 2px; border-top-right-radius: 12px; } .time-current { border: 2px solid black; } </style>{{cookbook/meetingPlanner.js}}
An example HTML form inspired by Days Calculator on timeanddate.com:
Enter future date: Submit <script type="text/javascript"> { // Do initialization that doesn't necessarily need to be included in // the example; see 'Calendar input element' const futureDatePicker = document.querySelector('input[name="futuredate"]'); const browserCalendar = new Intl.DateTimeFormat().resolvedOptions().calendar; const today = Temporal.Now.plainDate(browserCalendar); futureDatePicker.min = today; futureDatePicker.value = today.add({ months: 1 }); {{cookbook/futureDateForm.js}} } </script>{{cookbook/futureDateForm.js}}
Take the difference between two Temporal.Instant
instances as a Temporal.Duration
instance (positive or negative), representing the duration between the two instants without using units coarser than specified (e.g., for presenting a meaningful countdown with vs. without using months or days).
{{cookbook/getElapsedDurationSinceInstant.mjs}}
Map a Temporal.Instant
instance and a Temporal.TimeZone
object into a Temporal.Instant
instance representing the nearest following exact time at which there is an offset transition in the time zone (e.g., for setting reminders).
{{cookbook/getInstantOfNearestOffsetTransitionToInstant.mjs}}
This example takes a roster of wall-clock opening and closing times for a business, and maps an exact time into a time-sensitive state indicator ("opening soon" vs. "open" vs. "closing soon" vs. "closed").
{{cookbook/getBusinessOpenStateText.mjs}}
Map localized trip departure and arrival times into trip duration in units no larger than hours. (By default, differences between ZonedDateTime instances are exact differences in time units.)
{{cookbook/getTripDurationInHrMinSec.mjs}}
Given a departure time with time zone and a flight duration, get an arrival time in the destination time zone, using time zone-aware math.
{{cookbook/getLocalizedArrival.mjs}}
Add the number of days it took to get an approval, and advance to the start of the following month.
{{cookbook/plusAndRoundToMonthStart.mjs}}
When considering a record (for example, a personal-best time in a sport), you might want to receive an alert just before the record is about to be broken.
This example takes a record as a Temporal.Duration
, the starting exact time of the current attempt as a Temporal.Instant
, and another Temporal.Duration
indicating how long before the potentially record-setting exact time you would like to receive an alert.
It returns the exact time at which a notification could be sent, for example "Keep going! 5 more minutes and it will be your personal best!"
This could be used for workout tracking, racing (including long and potentially time-zone-crossing races like the Bullrun Rally, Iditarod, Self-Transcendence 3100, and Clipper Round The World), or even open-ended analogs like event-every-day "streaks".
{{cookbook/getInstantBeforeOldRecord.mjs}}
Example of getting a Temporal.PlainDate
representing the first Tuesday of the given Temporal.PlainYearMonth
, adaptable to other weekdays.
{{cookbook/getFirstTuesdayOfMonth.mjs}}
Given a Temporal.PlainYearMonth
instance and an ISO 8601 ordinal calendar day of the week ranging from 1 (Monday) to 7 (Sunday), return a chronologically ordered array of Temporal.PlainDate
instances corresponding with every day in the month that is the specified day of the week (of which there will always be either four or five).
{{cookbook/getWeeklyDaysInMonth.mjs}}
Given a Temporal.PlainDate
instance, return the count of preceding days in its month that share its day of the week.
{{cookbook/countPrecedingWeeklyDaysInMonth.mjs}}
Here are some examples of taking an existing date, and adjusting the day of the month.
{{cookbook/adjustDayOfMonth.mjs}}
Likewise, here are some examples of taking an existing date and adjusting the month, but keeping the day and year the same.
Depending on the behavior you want, you will need to pick the right overflow
option, but the default of "constrain"
should be correct for most cases.
{{cookbook/adjustMonth.mjs}}
From a Temporal.ZonedDateTime
instance, get a Temporal.ZonedDateTime
representing the next occurrence of a weekly event that is scheduled on a particular weekday and time in a particular time zone. (For example, "weekly on Thursdays at 08:45 California time").
{{cookbook/nextWeeklyOccurrence.mjs}}
In some countries, when a public holiday falls on a Tuesday or Thursday, an extra "bridge" public holiday is observed on Monday or Friday in order to give workers a long weekend off. The following example calculates this.
{{cookbook/bridgePublicHolidays.mjs}}
These are not expected to be part of the normal usage of Temporal
, but show some unusual things that can be done with Temporal
.
Since they are generally larger than these cookbook recipes, they're on their own pages.
Extend Temporal
to support arbitrarily-large years (e.g., +635427810-02-02) for astronomical purposes.