victory

About

Data viz for React

What detecting victory tells you about a site

victory is Formidable's React charting library, built entirely from composable SVG components, so finding it tells you the team wanted charts they could assemble and restyle declaratively in React rather than configuring a monolithic chart object. It reads as a deliberate, React-idiomatic data-visualisation choice, common in dashboards and analytics products that value component-level control. Because it renders SVG component trees, it suits moderate datasets and customised visuals more than massive high-frequency data, which itself hints at the scale of data the app handles.

Why the exact victory version matters

Victory's major versions reorganised its component API and theming and updated React peer requirements, so the version pins which charting components and props the build relies on and which React era it sits in. As with most React libraries that have been around several years, the major also dates the project and signals how actively the visualisation layer is maintained.

victory in a real-world stack

When you find victory in a bundle, it rarely travels alone. React, and on native apps victory-native; otherwise a dashboard UI kit.

Quick facts

Common pairings

Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.

What victory pulls in

victory declares 27 direct dependencies — each one also rides into any bundle that ships victory, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .

How Sourcemap Explorer detects victory

victory ships as v37.3.6, published 2025-01-14 and carries 27 direct dependencies, 1 peer dependency (react), 270 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when victory rides inside a deployed bundle — here is how the detection works.

We catch victory from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/victory/ 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. 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 `victory` paths live.

2. 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/victory/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/victory/package.json` gives you the exact installed version.

3. 3

   Read the version directly from package.json

   Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/victory/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.

Major releases of victory

When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the victory version a site actually ships against the ecosystem.

Recent versions

victory README

Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.

an ecosystem of composable React components for building interactive data visualizations.

Victory

Contents

• Getting Started
• Victory Native
• API Documentation
• Guides
• Contributing

• See the docs and examples on the website: https://commerce.nearform.com/open-source/victory
• Experiment with all Victory components in this code sandbox

Getting started

1. Add Victory to your project:

# npm
$ npm i --save victory
# or yarn
$ yarn add victory

1. Add your first Victory component:

import React from "react";
import { render } from "react-dom";
import { VictoryPie } from "victory";

const PieChart = () => {
  return <VictoryPie />;
};

render(<PieChart />, document.getElementById("app"));

1. VictoryPie component will be rendered, and you should see:

Requirements

Projects using Victory should also depend on React. As of victory@34.0.0 Victory requires React version 16.3.0 or above

Victory Native

Victory Native shares most of its code with Victory, and has a nearly identical API! To learn more, check out the Victory Native package README.

Contributing

Please see the Contributing guide.

Maintenance Status

Active: Formidable is actively working on this project, and we expect to continue to work for the foreseeable future. Bug reports, feature requests and pull requests are welcome.

FAQ

Keep reading on Sourcemap Explorer