Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

intl-list-format

Package Overview
Dependencies
Maintainers
1
Versions
4
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

intl-list-format

A fully spec-compliant polyfill for 'Intl.ListFormat'

  • 1.0.3
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
8.4K
increased by11.12%
Maintainers
1
Weekly downloads
 
Created
Source
Logo

A fully spec-compliant polyfill for 'Intl.ListFormat'

Downloads per month NPM version Dependencies Contributors code style: prettier License: MIT Support on Patreon

Description

This is a 1:1 implementation of the Intl.ListFormat draft spec proposal ECMA-402, or the ECMAScript® Internationalization API Specification.

The Intl.ListFormat object is a constructor for objects that enable language-sensitive list formatting. It is a really useful low-level primitive to build on top of which avoids the need to parse lots of CLDR raw data at the expense of your users and their internet connections.

It builds upon another member of the Intl family: Intl.getCanonicalLocales, so this must be polyfilled. See this section for an overview.

This implementation passes all 134 Test262 Conformance tests from the Official ECMAScript Conformance Test Suite.

Features

Some highlights of this polyfill include:

  • A very precise implementation of the spec, with cross-references inlined in the source code
  • Conditional loading of Locale data for all CLDR locales
  • Well-tested and well-documented.
  • Passes all Official ECMAScript Conformance Tests

Table of Contents

Install

NPM

$ npm install intl-list-format

Yarn

$ yarn add intl-list-format

Applying the polyfill

The polyfill will check for the existence of Intl.ListFormat and will only be applied if the runtime doesn't already support it.

To include it, add this somewhere:

import "intl-list-format";

// Or with commonjs:
require("intl-list-format");

However, it is strongly suggested that you only include the polyfill for runtimes that don't already support Intl.ListFormat. One way to do so is with an async import:

if (!("ListFormat" in Intl)) {
	await import("intl-list-format");

	// or with commonjs:
	require("intl-list-format");
}

Alternatively, you can use Polyfill.app which uses this polyfill and takes care of only loading the polyfill if needed as well as adding the language features that the polyfill depends on (See dependencies).

Loading locale data

By default, no CLDR locale data is loaded. Instead, you decide what data you want. To load data, you can import it via the /locale-data subfolder that comes with the NPM package:

With ES modules:

// Load the polyfill
import "intl-list-format";

// Load data for the 'en' locale
import "intl-list-format/locale-data/en";

And naturally, it also works with commonjs:

// Load the polyfill
require("intl-list-format");

// Load data for the 'en' locale
require("intl-list-format/locale-data/en");

Remember, if you're also depending on a polyfilled version of Intl.getCanonicalLocales, you will need to import that polyfill beforehand.

Usage

The following examples are taken directly from the original proposal

Intl.ListFormat.prototype.format

// Create a list formatter in your locale
// with default values explicitly passed in.
const lf = new Intl.ListFormat("en", {
	localeMatcher: "best fit", // other values: "lookup"
	type: "conjunction", // "conjunction", "disjunction" or "unit"
	style: "long" // other values: "short" or "narrow"
});

lf.format(["Motorcycle", "Truck", "Car"]);
// > "Motorcycle, Truck, and Car"

Intl.ListFormat.prototype.formatToParts

const lf = new Intl.ListFormat("en");
lf.formatToParts(["Foo", "Bar", "Baz"]);
// > [
// >   {type: "element", value: "Foo"},
// >   {type: "literal", value: ", "},
// >   {type: "element", value: "Bar"},
// >   {type: "literal", value: ", and "},
// >   {type: "element", value: "Baz"}
// > ]

Intl.ListFormat.prototype.resolvedOptions

const lf = new Intl.ListFormat("en", {type: "unit", style: "narrow"});

lf.resolvedOptions();
// > {locale: "en", style: "narrow", type: "unit"}

Intl.ListFormat.supportedLocalesOf

Intl.ListFormat.supportedLocalesOf(["foo", "bar", "en-US"]);
// > ["en-US"]

Dependencies & Browser support

This polyfill is distributed in ES3-compatible syntax, but is using some additional APIs and language features which must be available:

  • Array.prototype.includes
  • Object.create
  • String.prototype.replace
  • Symbol.toStringTag,
  • WeakMap
  • Intl.getCanonicalLocales

For by far the most browsers, these features will already be natively available. Generally, I would highly recommend using something like Polyfill.app which takes care of this stuff automatically.

Contributing

Do you want to contribute? Awesome! Please follow these recommendations.

Maintainers

Frederik Wessberg
Frederik Wessberg
Twitter: @FredWessberg
Lead Developer

Backers

Patreon

Become a backer and get your name, avatar, and Twitter handle listed here.

Backers on Patreon

FAQ

What is the default locale?

The default locale will be equal to the locale file you load first.

Are there any known quirks?

Nope!

License

MIT © Frederik Wessberg (@FredWessberg) (Website)

Keywords

FAQs

Package last updated on 09 Jul 2019

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc