Closed aberenyi closed 3 years ago
I suspect it's a bundler issue. Are you using a bundler and ES6 modules, or using pre-bundled D3?
dc.js 4.2 will use d3@6 by default, but it still works with d3@5. If you are using pre-bundled D3, a workaround could be to force d3@5.
If you are using a bundler with ES6 modules, I have seen a lot of conversations that recommend
import 'd3-transition';
E.g. see d3/d3-selection#185
This was indeed a bundler issue.
I've tried various things - not quite sure which one did the trick.
Anyways, thanks for the lightning fast response, closing.
I've tried various things - not quite sure which one did the trick.
Haha, yes, that is the most common solution! Which is why this stuff never gets documented properly.
Hi,
After upgrading to
4.2.0
(from4.0.3
) I ran into this issue:Also happens w/ composite line charts:
The source is most likely the
1.3.2
->2.0.0
bump ofd3-transition
.I'll try to come up with a workaround - any help finding the cause of this would be appreciated.
Cheers
p.s. found this ancient https://github.com/d3/d3/issues/3262 issue, but I'm virtually certain it's not related