victory

About

Data viz for React

Live mirror of the GitHub README. 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.

Quick facts

Common pairings

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

How Sourcemap Explorer detects victory

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.

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.

Recent versions

FAQ

Keep reading on Sourcemap Explorer