Package Exports

accept-language-parser

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (accept-language-parser) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

accept-language-parser

Dependencies

Parses the accept-language header from an HTTP request and produces an array of language objects sorted by quality.

Installation:

npm install accept-language-parser

API

parser.parse(acceptLanguageHeader)

var parser = require('accept-language-parser');

var languages = parser.parse('en-GB,en;q=0.8');

console.log(languages);

Output will be:

[
  {
    code: "en",
    region: "GB",
    quality: 1.0
  },
  {
    code: "en",
    region: undefined,
    quality: 0.8
  }
];

Output is always sorted in quality order from highest -> lowest. as per the http spec, omitting the quality value implies 1.0.

parser.pick(supportedLangugagesArray, acceptLanguageHeader, options = {})

Alias: parser.pick(supportedLanguagesArray, parsedAcceptLanguageHeader)

var parser = require('accept-language-parser');

var language = parser.pick(['fr-CA', 'fr-FR', 'fr'], 'en-GB,en-US;q=0.9,fr-CA;q=0.7,en;q=0.8');

console.log(language);

Output will be:

"fr-CA"

The options currently supports only loose option that allows partial matching on supported languages. For example:

parser.pick(['fr', 'en'], 'en-GB,en-US;q=0.9,fr-CA;q=0.7,en;q=0.8');

Would return:

"fr"

In loose mode the order of supportedLanguagesArray matters, as it is the first partially matching language that is returned. It means that if you want to pick more specific langauge first, you should list it first as well, for example: ['fr-CA', 'fr'].

Running test

npm install
npm test

License

MIT