About
Data-Driven Documents
What detecting d3 tells you about a site
d3 reveals bespoke, data-driven visualisation — the team is binding data to SVG/Canvas directly rather than using a chart component. Its presence signals custom charts, maps or interactive graphics that off-the-shelf libraries couldn't deliver, and usually a data- or dashboard-heavy product.
Why the exact d3 version matters
d3 is a meta-package of many d3-* modules, and apps frequently import only the submodules they need. The exact version (and which submodules are present) tells you how much of D3 actually ships and which generation of the scale/selection APIs the code targets.
d3 in a real-world stack
When you find d3 in a bundle, it rarely travels alone. Individual d3-* submodules; sometimes alongside a higher-level chart library for the simpler views.
Quick facts
npm install d3What d3 pulls in
d3 declares 30 direct dependencies — each one also rides into any bundle that ships d3, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .
How Sourcemap Explorer detects d3
d3 ships as v7.9.0, published 2024-03-12 and carries 30 direct dependencies, 273 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when d3 rides inside a deployed bundle — here is how the detection works.
We catch d3 from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/d3/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `d3` paths live.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/d3/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/d3/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/d3/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Major releases of d3
When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the d3 version a site actually ships against the ecosystem.
Recent versions
d3 README
Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.
D3: Data-Driven Documents
D3 (or D3.js) is a free, open-source JavaScript library for visualizing data. Its low-level approach built on web standards offers unparalleled flexibility in authoring dynamic, data-driven graphics. For more than a decade D3 has powered groundbreaking and award-winning visualizations, become a foundational building block of higher-level chart libraries, and fostered a vibrant community of data practitioners around the world.
Daily downloads of D3 · oss-analytics
Resources
FAQ
What is d3 used for?
Data-Driven Documents
How can I tell if a website is using d3?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `d3` from two complementary signals: `node_modules/d3/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
How do I find out which version of d3 a website is running?
Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `d3/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/d3/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 7.9.0, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.
What is the latest version of d3?
7.9.0, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Is d3 actively maintained?
Quiet at the moment — no new release in over two years. Worth checking the repository for an active fork before adopting on a new project. The last published release was 2024-03-12. Source code: https://github.com/d3/d3.
Where can I read more?
Project homepage: https://d3js.org. Source code: https://github.com/d3/d3. Published on npm: https://www.npmjs.com/package/d3. Licensed as ISC.
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for d3 and report the precise version (the registry's latest is v7.9.0, published 2024-03-12; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.