Dc.js Versions Save

Multi-Dimensional charting built to work natively with crossfilter rendered with d3.js

4.0.0

4 years ago

Please see the Changelog for detailed release notes.

The GitHub Releases are not current; there are later 4.* releases (up to 4.2.7) on npm, and dc-v5 is on a branch..

3.0.2

6 years ago

Please see the Changelog for detailed release notes. We don't currently use GitHub Releases for release notes.

Use dc.js version 3.* if you want compatibility with d3 versions 4 and 5. Use dc.js version 2.* if you want compatibility with d3 version 3. 2.* will be maintained for a limited time.

2.0.2

7 years ago

This is the stable release of dc.js.

Please see the changelog for the latest features and bug fixes.

2.0.1

7 years ago

This is the stable release of dc.js.

See the changelog for the latest features and bug fixes.

2.0.0

7 years ago

This is the stable release of dc.js.

See the changelog for the latest features and bug fixes.

2.0.0-beta.26

8 years ago

This is mainly a documentation release.

Please watch the Changelog for release notes.

(We don't have a huge need for GitHub Releases, but it might be nice to copy the changelog here.)

1.7.5

8 years ago

Requested in #1023 - and until 2.0 goes live, we have to update the 1.7 branch in order to add stuff to cdnjs.

So, this still-unsupported branch gets another update.

2.0.0-beta.19

8 years ago

dc.js 2.0 is very close to a release - please try out this beta!

Among other changes, beta 19 is a lot faster, because it enables crossfilter optimizations which had been previously unused.

See the changelog for complete details.

1.7.4

8 years ago

This release just brings the sourcemaps *.map into the distribution so that Chrome will stop complaining about them being missing.

The 1.7.* branch is still unsupported and its tests fail. Release 2.0 is almost here, please try the latest beta.

1.7.3

9 years ago
  • Some corrections to module support for browserify and other node-based modularization schemes
  • Note: tests are broken on this release, and will not be fixed (unless someone cares to contribute). This is mostly due to changes in d3.js. Tests work properly in 2.*