resolve-accept-language - npm Package Compare versions

Comparing version 1.0.36 to 1.0.37

package.json

		{
		"name": "resolve-accept-language",
		"version": "1.0.36",
		"version": "1.0.37",
		"description": "Resolve the preferred locale based on the value of an `Accept-Language` HTTP header.",
		@@ -41,15 +41,15 @@ "author": "Avansai (https://avansai.com)",
		"@types/jest": "^27.0.2",
		"@typescript-eslint/eslint-plugin": "^5.0.0",
		"@typescript-eslint/parser": "^5.0.0",
		"@typescript-eslint/eslint-plugin": "^5.1.0",
		"@typescript-eslint/parser": "^5.1.0",
		"dotenv-cli": "^4.0.0",
		"eslint": "^8.0.1",
		"eslint": "^8.1.0",
		"eslint-config-prettier": "^8.3.0",
		"eslint-plugin-jest": "^25.2.2",
		"jest": "^27.3.0",
		"jest": "^27.3.1",
		"prettier": "2.4.1",
		"release-it": "^14.11.6",
		"ts-jest": "^27.0.7",
		"ts-node": "^10.3.0",
		"ts-node": "^10.4.0",
		"typescript": "^4.4.4"
		}
		}

README.md

		@@ -46,3 +46,3 @@ # resolve-accept-language
		- Using 2 letter language codes is rarely sufficient. Without being explicit about the targeted country for a given language, it is impossible to provide the right format for some content such as dates and numbers. Also, while languages are similar across countries, there are different ways to say the same thing. Our hypothesis is that by better targeting the audience, the user experience will improve.
		- About 99% of all cases can be covered using the `language`-`country` format. We could possibly extend script support in the future but one the approach being this library is to keep it as simple as possible, while providing the best match.
		- About 99% of all cases can be covered using the `language`-`country` format. We could possibly extend script support in the future given a valid use case, but in the meantime our goal is to keep this library as simple as possible, while providing the best matches.

		@@ -49,0 +49,0 @@ ## How does the resolver work?

New alerts