Array manipulation, ordering, searching, summarizing, etc.

Image Sharpening

Mike Bostock

d3.blur

d3.rank

d3.flatGroup, d3.flatRollup

d3.mode

d3.groupSort

Set Operations

d3.groups as a hierarchy

d3.fsum, d3.Adder

Time thresholds for d3.bin

d3.cumsum

Tidy Stacked Area Chart

Merging Duplicate Values

d3.zip, d3.transpose

d3.bin

d3.ticks

d3.mean, d3.median, and friends

d3.quickselect

d3.bisect

d3.sum

d3.group, d3.rollup, d3.index

d3.count

d3.min, d3.max, d3.extent

d3.least, d3.greatest

d3.pairs

d3.cross

d3.ascending, d3.descending

d3.merge

d3.range

d3.permute

d3.shuffle

d3-array 2.0

D3 Documentation

d3-array

2D layout algorithms for visualizing hierarchical data.

d3-hierarchy

Hey Fil, is there a use case for a custom children accessor when working with Maps?

Ben Ayre

I don't have one in mind but if you need to create one you can use the mapChildren function (which is used internally) as a template :
d3.hierarchy(group, function mapChildren(d) { return Array.isArray(d) ? d[1] : null; })

Thanks! I can't see one either and I'm wondering if it's an unnecessary vulnerability. If the accessor returns an iterable it appears to crash (try d => d or d => "anything"). I can open an issue if you think it's warranted. Feel free to remove these comments 🙃

if the children accessor always returns children then you get an infinite loop, which crashes the browser as expected ;) At some point you need to stop the chain.

Here's a fun example:
d3.hierarchy("root", d => {
  const n = d3.randomBinomial(30, 1 / d.length)();
  if (n) return new Array(n).fill(`child of ${d}`);
})