On Tue, Mar 05, 2024 at 05:39:00PM +0530, Nilesh Patra wrote: > On Mon, Mar 04, 2024 at 09:18:01PM +0000, Julian Gilbey wrote: > [...] > > (!) Conflicting re-exports > > "index.js" re-exports "map" from both > > "../../../usr/share/nodejs/d3-array/src/index.js" and > > "../../../usr/share/nodejs/d3-collection/src/index.js" (will be ignored). > > created dist/d3.min.js in 4.2s > > ----- > > I have pushed a commit to salsa that hopefully fixes this - can you please > try with the same and see if that > helps you somewhat?
That's perfect, thanks! And such a simple solution :-) (Though I don't pretend to understand how the patch works!) The taskflow webserver now works exactly as intended (as far as I can tell). > > So it's specifically "map" that is problematic, and I just happen to > > have stumbled upon it: d3 v5 depends on d3-array version 1, but the > > version of node-d3-array in unstable is 3.2.0+~cs5.0.6-2, and this is > > causing the conflict. > > > > I don't know the best way to fix this. node-d3-array version was > > upgraded from 1.2.4 to 3.x about two years ago, so d3 would have had > > this bug since then, but I'm the first one to stumble upon it :-/ > > > > Perhaps we could package node-d3-array-1 (version 1.2.4) and have > > node-d3 build-depends on that? > > I tried to embed it and realised it is creating an unholy mess. I got it > working eventually > but it can open a can of worms sometime later. Maybe packaging the older > version > would be the way to go if my fix above does not work. > > I've added yadd to the thread for more qualified advice. It might be a good idea to do this anyway, but given that no-one else has noticed a problem in > 2 years suggests it's not worth the effort. Best wishes, Julian
