More complications with dependencies #36
Description
I'm not sure if we can get around this one easily, but I want to log a problem I just saw.
Package A depends on package B, which depends on package C. Package B actually modifies package C to expose itself (in my case, B is jqueryui and C is jquery). Package A bundles B version 1 and C version 2.
Package B doesn't care what version of C it uses.
Package D also depends on A and on C (version 1). Package D pulls in package B version 1, and has package C version 1 and version 2 bundled. Package D's bundle is mangled to have package B relying on package C version 1 (instead of C version 2!).
Now when things are loaded on the page, we get D's bundled package B, which pulls C version 1 and modifies it, but then when we try to use C version 2 inside package A, it breaks. (In my case, I had jquery-ui modifying jquery version 2 from bqplot, instead of modifying jquery version 3 from ipywidgets).
I think this would be solved if somehow the bundling of package D realized that B came from A, so it should use A's version of C when mangling B's imports.