On Thu, Apr 24, 2014 at 4:14 AM, Ramakrishnan Muthukrishnan
> Package: libjs-d3
> Version: 3.4.6-1
> Severity: normal
> I noticed that the d3.js generated by the Debian package is very
> different from the d3.js shipped with the upstream tarball. I don't
> know at this point, if any functionality is affected. But a simple
> diff a lot of changes.
I've several complex examples locally. Those works normally.
> One of the reason for this could be that the d3 upstream package
> requires uglify version 2.4.0 where as the d3 debian package is
> using the one shipped with Debian, which is 1.3.4.
Yes, this is the reason. UglifyJS does several alternations, not
affecting the code itself. As such, the UglifyJS build dependency is
not a hard one.
> I have raised
> a wishlist bug against the node-uglify package (#745687) requesting
> an upgrade of the uglify package. I don't know at this point if
> this will fix the problem.
That would 'fix' it, ie it would look like the same to the one from upstream.
But please note that UglifyJS 1.x  and 2.y  are different
projects, developed differently and not an upgrade.
I'd like to see UglifyJS2 2.y packaged as well, but it seems the