tglase@tglase-nb:~ $ uglifyjs --version
	2.8.29

This is after an upgrade. Before, it output:
	uglify-js 2.8.29

There was apparently no change to the node-uglify package itself,
only to some *other* nodejs packages.

Please explain how this comes to be. This broke our build, which
uses the output of “uglifyjs --version 2>/dev/null” to determine
whether 2.x or 3.x was used, to prevent too-new versions (as some
coworkers use Canonical’s software museum together with npm, in‐
stead of getting all dependencies via Debian).

To me, outputting a version number is a simple WriteLn/echo/print{,f}
command. Why and how can this change if a dependency changes? Which
dependency was it, and what else does this change affect?

tests of uglifyjs passed with the new node-yargs.

Dear submitter,

as the package uglifyjs has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1127304

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)