package.json refers to non-existent d3 v3.0 tag

[d3]

package.json refers to non-existent d3 v3.0 tag

[jasondavies]

I assume you mean Bower. :)

This works fine with npm. The 3.0 refers to any git ref, in this case the 3.0 branch.

The d3.geo.projection plugin in master requires D3 V3 for the tests to pass. I only really added package.json so that you can easily run npm install followed by npm test.

It looks like Bower only supports tags at the moment, see bower/bower#107 for a long and inconclusive discussion about it.

Since v3.0 is under development, it might be simpler for you to wait until it's released and tagged, and just copy the plugin files that you need in the meantime. I view d3-plugins more as a collection of plugins rather than a single versioned package, so I prefer to copy individual plugins when I use them.

[shawnbot]

Er yeah, Bower :)

Fair enough, though. I was just starting to like the idea of doing bower install d3-plugins to get them into a new project. I'm happy to keep a checkout of d3-plugins around and copy individual plugins as needed for now. Thanks!