D3 v4.0 namespaced imports are actually encouraged

[caesarsol]

Hello,
there is a small inaccuracy in your documentation.
In the README you say:

A small thing — it's possible to use only parts of d3. For example: import {voronoi as d3Voronoi} from 'd3-voronoi'; instead of d3.voronoi, and import {lab} from 'd3-color'; instead of d3.color.lab), but nobody uses it that way, so examples of the import style are hard to find (and it's often not obvious which name will be exported (d3-geo exports geoArea and geoBounds rather than area and bounds).

Actually, the namespacing is a powerful feature and using it is encouraged in d3v4:

If you don’t care about modularity, you can mostly ignore this change and keep using the default bundle. However, there is one unavoidable consequence of adopting ES6 modules: every symbol in D3 4.0 now shares a flat namespace rather than the nested one of D3 3.x. For example, d3.scale.linear is now d3.scaleLinear, and d3.layout.treemap is now d3.treemap.

See the official migration guide (and specifically this namespace migration table for the d3-geo library)

[joelburget]

I agree, modularity is the bomb. I wouldn't ever discourage it! But I maintain there are very few examples of its use today.