Intl.RelativeTimeFormat.prototype.resolvedOptions() method returns a new object with properties reflecting the locale and relative time formatting options computed during initialization of this
The source for this interactive example is stored in a GitHub repository. If you'd like to contribute to the interactive examples project, please clone https://github.com/mdn/interactive-examples and send us a pull request.
A new object with properties reflecting the locale and number formatting options computed during the initialization of the given
The resulting object has the following properties:
- The BCP 47 language tag for the locale actually used. If any Unicode extension values were requested in the input BCP 47 language tag that led to this locale, the key-value pairs that were requested and are supported for this locale are included in
- The length of the internationalized message. Possible values are:
long" (default, e.g.,
in 1 month)
in 1 mo.),
- or "
in 1 mo.). The narrow style could be similar to the short style for some locales.
- The format of output message. Possible values are:
always" (default, e.g.,
1 day ago),
- or "
yesterday). The "
auto" value allows to not always have to use numeric values in the output.
- The value requested using the Unicode extension key "
nu" or filled in as a default.
var de = new Intl.RelativeTimeFormat('de-DE'); var usedOptions = de.resolvedOptions(); usedOptions.locale; // "de-DE" usedOptions.style; // "long" usedOptions.numeric; // "always" usedOptions.numberingSystem; // "latn"
|ECMAScript Internationalization API (ECMA-402)
The definition of 'RelativeTimeFormat.resolvedOptions()' in that specification.
BCD tables only load in the browser