External access to locale definitions?

[jheer]

Prior to wide-scale ES6 adoption, the locale definitions are not externally available. For example, they are not included in the built ES5 files. Only the pre-specified default locale is included. It would be helpful to be able to access the locale definitions for convenient specification and switching. (Note that this applies to d3-time-format as well.)

We recently updated datalib to support runtime locale switching (in particular, this was requested by Wikipedia folks for their Vega graph support), but this requires passing in a full JSON blob of locale settings. To make these settings accessible, one options for us is to build out a separate repo that contains a registry of locale definitions (i.e., one that can be included as a project dependency). However, that would simply replicate the work you've done here, and so seems both inelegant and prone to inconsistency due to code drift.

Any plans / thoughts in this regard? One option might be to include the locales in the build (though bloating the file size). Another might be a parallel build that exports just the locale definitions, perhaps as a single JSON file keyed by locale id.

[mbostock]

I think it’s simplest to include them by default and allow people to optimize file sizes by making a custom build to prune functionality if they so desire. Fixed in 0.3.0!

[jheer]

Fantastic. Thanks!

[mbostock]

Following up on this, as I decided to take the locales out of the code and instead represent them as JSON files so they can be loaded dynamically. They are published to NPM, so one option is to load them from npmcdn:

https://npmcdn.com/d3-format@0.6.0/locale/zh-CN.json

You can replace the “0.6.0” with any semver range, or omit the @ and range entirely if you want the latest version:

https://npmcdn.com/d3-format/locale/zh-CN.json

[iosonosempreio]

D3 locale definitions are very convenient, thanks!
What is the best way to access the complete list of built-in locale in d3-format?