Including d3-fetch.v1.js causes d3.svg to be undefined in nv.d3.js about d3-fetch

[mbostock]

Sounds like both d3-fetch and NVD3 define d3.svg, so you won’t be able to use them together. Sorry!

[gordonwoodhull]

Generally, you can't include d3@3 and d3@4+ in the same HTML file.

I needed to load d3v4-force into a d3@3 project and I had luck using rollup to produce a bundle that exposed the d3@4 code as d3v4 instead of d3.

https://github.com/dc-js/dc.graph.js/blob/develop/d3v4-force.rollup.config.js

(Doing a sed search-and-replace also worked, but this is more elegant.)

[JetForMe]

Sounds like both d3-fetch and NVD3 define d3.svg, so you won’t be able to use them together. Sorry!

Why does something designed for fetching data define d3.svg?

Generally, you can't include d3@3 and d3@4+ in the same HTML file.

I was aware the NVD3 couldn't use d3 v4, but I thought I was avoiding that, following their examples. I'm not using node, so I'm not sure how to incorporate your solution.

[JetForMe]

Oh I see, you parse SVG. I think I'll just modify my copy to change the definition.

[JetForMe]

Or maybe you could make everything live under d3.fetch?

[mbostock]

Sorry, but I’m not going to rename this method. The d3.svg namespace was removed from D3 in 4.0 which was released in 2016. This module added a new d3.svg method (parallel to d3.xml, d3.text, d3.json, etc.) in 2018.

[gordonwoodhull]

d3-fetch is circa d3@5 so it’s not compatible with d3@3 used by NVD3.

My rollup solution has nothing to do with Node. It’s just a way to bundle individual D3 ES6 modules to replaced3-fetch.v1.js with something that don’t write to the global d3 namespace.

It’s basically the same way the official D3 bundles are created.

[JetForMe]

Ah I see. Well, I did search and replace, which worked, but then couldn't get NVD3 to do what I wanted, to I switched to C3.