Since 3.1, the Mercator projection does not clamp y-values. For rendering
latitudes near the pole, the y-values can approach infinity. Rather than
clamping each point in the projection, d3.geo.mercator now sets the clipExtent
automatically (if not overridden) using the projection's scale and translate.

Previous versions of JSDOM erroneously returned null rather than the empty
string, but this has now been fixed. Note: this depends on tmpvar/jsdom#582
which has not yet been merged to master.

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