I'm sorry for bothering again (yes it's me 😞 ), but I just discovered I cannot use lcid in my company, because it depends on [email protected], which is missing a full license text in the distribution. invert-kv@2 is fine, probably because it was published with a more recent version of the npm tool.

I noticed the version bump in invert-kv was done due to dropping a support for old Node versions. lcid still seems to support even node 0.10. Thus I think there are two solutions to that:

1. To just re-publish invert-kv as it is, with a recent npm version, which automatically includes the license file in the distribution. It could be released as [email protected] and as such it could propagate automatically, fixing any project depending on ^1.0.0, including lcid (and anything depending on lcid, e.g. yargs or nconf).

2. To drop old node versions support here and upgrade lcid to use invert-kv@^2, but that would mean breaking change for lcid as well and wouldn't automatically propagate through the ecosystem.

I'm sorry again for being a PITA, but when the full text is missing, our lawyers consider the code unlicensed, thus fully copyrighted and unusable as open source.

Hi, I compared the Microsoft LCID standards and found some of the LCID don't exist in this project.
For example en-sg, which is Singapore English with the LCID 18441.

• Microsoft LCID List

Hello
I'm experiencing issues with the Spanish locale.
In the mappings, there are two different codes for Spanish:

0x040a: "es_ES", # Spanish - Spain
0x0c0a: "es_ES", # Spanish - Spain (Modern)

The first one unfortunately doesn't work when calling the from method.

from(1034); // undefined

Those two methods can return undefined since any string or any number can be passed in.

I opened a PR with a proposed solution here.

I mean, are all available standard language codes part of the database or just the ones for which there is a windows equivalent?

Hello,

Thanks for your work.

Why do you use _ in your locale (ex: en_US) when RFC speak about hypen - (ex: en-US) ?

https://tools.ietf.org/html/rfc4646#page-4

Thanks.