Any blocker not to bump to last majors of d3-*?

[dubzzz]

Is your feature request related to a problem? Please describe.

Yes and no. I observed that nivo was pulling multiple versions of some d3- packages. While trying to suggest changes to dedupe them I detected that many d3- dependencies was outdated by several majors.

Describe the solution you'd like

Bumping to latest major of d3-.

Describe alternatives you've considered

Keep it that way.

Additional context

Before opening any PR in that direction I wanted to confirm that it would be ok to go in that direction.

[plouc]

First, the fact that D3 packages moved to esm, also that D3 now requires a browser that supports ES2015. That being said, I already had to upgrade d3-color due to a security issue, so it would be a continuation of this update. Other than that, just the fact that D3 APIs have changed and nivo doesn't have a consistent code coverage depending on the package. We can see a summary of the changes per major here, and there are a few breaking changes.

[dubzzz]

Indeed the esm-only is a huge blocker 😢

[plouc]

Yea, but I think we need to move forward anyway, other libraries relying on D3 faced the same issue, victory explained the issue in details here, but the infrastructure of nivo is already complex enough, I'd like to avoid to have to transpile and vendor D3 dependencies.

[plouc]

Seems like visx is also struggling with this...

[plouc]

I'm closing this as the main roadblock is now described in this issue: #2310.