ISO8601-duration

Node/Js-module for parsing and making sense of ISO 8601 durations

A new standard is on it's way, see Temporal.Duration
Tests (most) in this module now validate against @js-temporal/polyfill

The ISO 8601 duration format

TL;DR
PnYnMnWnDTnHnMnS - P<date>T<time>.
(P) Years, Months, Weeks, Days (T) Hours, Minutes, Seconds.
Example: P1Y1M1DT1H1M1.1S = One year, one month, one day, one hour, one minute, one second, and 100 milliseconds

Durations in ISO 8601 comes in 2 variants:

ISO 8601-1
Weeks are not allowed to appear together with any other units and durations can only be positive (used until v2.0.0 in this module).
Valid patterns with weeks: P2W.
Invalid patterns with weeks: P2W2D.

ISO 8601-2
An extension to the standard, allows combining weeks with other units (supported since v2.1.0 in this module).
Valid patterns with weeks: P2W & P2W2DT5H, etc.

ISO 8601-2 also allows for a sign character at the start of the string (-P1D, +P1M), this is not yet supported by this module.

PnYnMnWnDTnHnMnS - P<date>T<time>

• The n is replaced by the value for each of the date and time elements that follow the n.
• Leading zeros are not required.
• Fractions are allowed on the smallest unit in the string, e.g. P0.5D or PT1.0001S but not PT0.5M0.1S.

Check out the details on Wikipedia or in the coming Temporal.Duration spec.

Install

1npm install iso8601-duration

Also available on jsr.io/@tolu/iso-8601-duration

Usage

Most noteworthy of the interface is the ability to provide a date for toSeconds-calculations.
Why becomes evident when working with durations that span dates as all months are not equally long.
E.g January of 2016 is 744 hours compared to the 696 hours of February 2016.

If a date is not provided for toSeconds the timestamp Date.now() is used as baseline.

Interface

1export const toSeconds; // fn = (obj, date?) => number
2export const pattern;   // ISO 8601 RegExp
3export const parse;     // fn = string => obj
4export default {
5	toSeconds,
6	pattern,
7	parse
8}

Example

Simple usage

1import { parse, end, toSeconds, pattern } from "iso8601-duration";
2
3console.log(parse("P1Y2M4DT20H44M12.67S"));
4/* outputs =>
5{
6	years: 1,
7	months: 2,
8	days: 4,
9	hours: 20,
10	minutes: 44,
11	seconds: 12.67
12}
13*/
14
15console.log(toSeconds(parse("PT1H30M10.5S")));
16// outputs => 5410.5
17
18console.log(end(parse("P1D")));
19// outputs => DateObj 2017-10-04T10:14:50.190Z

A more complete usecase / example

1import { parse, toSeconds, pattern } from "iso8601-duration";
2
3// convert iso8601 duration-strings to total seconds from some api
4const getWithSensibleDurations = (someApiEndpoint) => {
5  // return promise, like fetch does
6  return new Promise((resolve) => {
7    // fetch text
8    fetch(someApiEndpoint)
9      .then((res) => res.text())
10      .then((jsonString) => {
11        // create new pattern that matches on surrounding double-quotes
12        // so we can replace the string with an actual number
13        const replacePattern = new RegExp(`\\"${pattern.source}\\"`, "g");
14        jsonString = jsonString.replace(replacePattern, (m) => {
15          return toSeconds(parse(m));
16        });
17        // resolve original request with sensible durations in object
18        resolve(JSON.parse(jsonString));
19      });
20  });
21};

License

MIT @ https://tolu.mit-license.org/