-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
handle d3v3, d3v4 conflicts with other htmlwidgets #4
Comments
Can you explain how to implement your current work around please? Where would I change "d3" to "d3v4"? Inside the d3.min of the particular package using v4? Or on the html page itself? Or somewhere else altogether? |
very painful and ugly example of a standalone build to prevent conflicts with window.d3 using different versions posted in https://github.com/timelyportfolio/sankeyD3/tree/standalone To complete the build, I
Then for now when calling |
conflict v3 to v4
Until other
htmlwidgets
have converted tod3v4
, the dependency management mechanism will choose the greatest version ford3
, which will bed3v4
. Then thewindow.d3
will be version 4 which will cause all other htmlwidgets on the page to fail. This will become more and more problematic, since the conversion by other widgets to d3 seems like it will be very slow.solutions?
I am not sure how best to handle, so I thought I would start the discussion. Currently I have only one solution and it is unfortunately not ideal.
d3v4
to bewindow.d3v4
or something other thanwindow.d3
. This is an easy change but would require all references tod3
to be changed tod3v4
. Also, it would mean we would have two sets ofd3
. Fortunately,d3
is not massive, but total would be about 500kb.The text was updated successfully, but these errors were encountered: