GitLab

The package name has now changed back to "uglify-js" on NPM.

We'll still use the major-versioned name file for d3js.org, but this is simpler.

Also, update node-canvas to v0.13.0 for better compatibility with
Node.js v0.8.x.

There appears to be a bug in Chrome causing the whole tab to crash when
setting svgNode.className.baseVal = "" for a newly-created element
without a non-empty class name:

  https://code.google.com/p/chromium/issues/detail?id=138552

This fix is a minor optimisation: if the current class is empty then
removing a class should be a no-op.  It also conveniently works around
the Chrome bug.

This reverts previous IE9 fixes to @4f552825.

We can finally re-enable those tests!

The update is to get the most recent version of contextify
which is a dependency of jsdom. Previous versions of 
contextify always generate a 64 library module. v0.6.11 of
node on macos is a 32-bit ARCH. The latest version of 
contextify  builds an ARCH that matches node NOT the arch
of the system.

See: https://github.com/brianmcd/contextify/issues/19

This allows you to require("d3") with no additional dependencies, and without
polluting the global namespace. Fixes #475.

Also, set vows version to "0.6.x" as the exact patch version is not
important right now.

Using "devDependencies" prevents "vows" etc. from being installed if D3
is being installed as a dependency. I'm not sure whether "jsdom" counts
as a true dependency or not as we only really use it for the tests.

I've also added a "scripts": {"test": …} parameter, which specifies what
happens when you run "npm test".

This required changing assert.length to assert.lengthOf in tests, due to
a Vows.js change to be compatible with Node.js v0.6.x.  For further
details:

    https://github.com/cloudhead/vows/pull/141

Fixes #340.

We still weren't sorting subgroups correctly. Also, we now sort chords by their
average value, rather than the source value, which works well with one-sided
chords (where either the source or target value is zero).

Due to the ordering in which the prototypes are defined, it was still undefined!
Also, the empty method depends on the node method being defined. Added a test.

It was previously possible for small differences in the reference time for
subtransitions. This could lead to tearing with expensive transitions, as some
transitions would have slightly different reference times than the others. This
is fixed by passing the reference time along explicitly when deriving a new
transition, either by the transition or selection operators.

I ran the tests on the newly minified files too, for good measure, and
everything passed.

We weren't computing the day-of-year number correctly, which affected both day
number and week number directives (%j, %U, and %W).

Also, expose d3.formatPrefix so that it's easier for callers to create a
formatter for a specific prefix (such as using the "G" prefix for all ticks).

This is better, because now we can enumerate all of our dependencies without
embedding them as submodules. After pulling, run `npm install`.