Update d3 to the latest version 🚀

[greenkeeper]

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 5.0.0 of d3 was just published.

Dependency	d3
Current Version	4.13.0
Type	devDependency

The version 5.0.0 is not covered by your current version range.

If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of d3.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.

---

Release Notes

5.0.0

• Remove d3-request; add d3-fetch.
• Remove d3-queue; see Promise.all.
• Add d3-scale-chromatic.
• Add d3-contour.
• Add selection.clone.
• Add d3.create.
• Add projection.angle.
• Remove d3.schemeCategory20* categorical color schemes. (See note below.)
• Fix duplicate installation of D3 modules at different versions. (#3256)
• Fix d3.format’s SI format for locales with currency suffixes.

D3 now includes new categorical color schemes from ColorBrewer, along with ColorBrewer’s excellent diverging, sequential single-hue and sequential multi-hue color schemes. The twenty-color schemes were removed because their grouped design often falsely implied non-existent relationships in the data: a shared hue can imply that the encoded data are part of a group (a super-category), while the relative lightness can falsely imply order.

Commits

The new version differs by 11 commits ahead by 11, behind by 2.

• 3fa7ace 5.0.0
• 82445ba 5.0.0-rc.4
• 44bace0 Remove d3-queue.
• 58477f6 Update API.
• 5fbfc8c Remove d3-queue. Fixes #3260.
• e1b691a Fix #3256 - don’t pin versions.
• 100483e Add yarn.lock.
• a85cfbd Update API.
• 7fc15ab Prepare for major release.
• f3ea70d Update API.
• 19c59ba Prepare for major release.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper bot 🌴

[bhousel]

It will probably be a while before we can take this upgrade, due to d3-request being deprecated. We will likely need to polyfill in both Fetch and Promise APIs if we want to continue to support IE11. (see current browser stats)

Full v5 changelog: https://github.com/d3/d3/blob/master/CHANGES.md

[greenkeeper]

Version 5.0.1 just got published.

Update to this version instead 🚀

Release Notes

v5.0.1

• Fix occasional overlap and hang in d3.packSiblings. Thanks, @robinhouston!

Commits

The new version differs by 11 commits.

• bbd0cb4 5.0.1
• b707ed5 Update d3-hierarchy.
• 4a7cc9f Update API.md
• 409ee40 Update CHANGES.md
• 932a66d Update CHANGES.md
• cfe28d8 Update CHANGES.
• 2b8ba30 Update CHANGES.
• 9bd8e37 Update CHANGES.
• 5f1e8bc Update CHANGES.
• 811ff50 Update API.
• b7e3516 Update CHANGES.

See the full diff

[greenkeeper]

Version 5.0.2 just got published.

Update to this version instead 🚀

Release Notes

v5.0.2

• Switch from D65 to D50 for Lab and HCL color spaces. Thanks, @danburzo!
• Fix Lab and HCL representation of achromatic colors.

Commits

The new version differs by 2 commits.

• 7a7e13e 5.0.2
• 2ff6e84 Update d3-color.

See the full diff

[greenkeeper]

Version 5.1.0 just got published.

Update to this version instead 🚀

Release Notes

v5.1.0

• Add d3.lch.
• Add d3.gray.
• Switch from D65 to D50 for Lab and HCL color spaces. Thanks, @danburzo!
• Fix Lab and HCL representation of achromatic colors.

Commits

The new version differs by 2 commits.

• 18e77c2 5.1.0
• 8a0140d Update d3-color.

See the full diff

[bhousel]

I'm working on this today. The main hurdle so far is swapping out d3-request for d3-fetch.

Today I learned that fetch was not abortable until somewhat recently, so we will need this AbortController polyfill so that our service code can continue to abort unneeded requests. This is a thing that can happen a lot as the user scrolls and iD requests data tiles, or when the user switches connection between prod<->dev osm servers.

[bhousel]

this has moved to #6245