$ npm install victory --save
VictoryPiecomponent will be rendered, and you should see:
Want to use
Victory with React Native? Check out victory-native
Victory Native shares most of its code with Victory, and has a nearly identical api!
victory repo aggregates stable victory components that are developed in other repos. The
repo is only updated with new releases, but the following repos are under very active development.
Please review our Code of Conduct before contributing.
For a detailed contribution guide, please see CONTRIBUTING in the project builder archetype.
# Clone the Victory repo$ git clone email@example.com:FormidableLabs/victory.git$ cd victory# Run the demo app server$ npm start# Open the demo app$ open http://localhost:3000# Run checks (lint and tests)$ npm test
For more on the development environment, see DEVELOPMENT in the project builder archetype.
This project is in alpha release. We're hard at work fixing bugs and improving the API. Be prepared for breaking changes!
SEMVER Minor version bumps should be considered breaking changes until we hit v1.0.0. Patches can be considered safe.
Caveats git installs using npm 2 may fail in postinstall. If you are consuming Victory via git installs please use npm >=3.0.0
If you want to use Jest snapshot testing
with Victory, you may encounter a problem where the Jest snapshot changes every time, due to a randomly generated
being used for a
VictoryClipContainer group component.
The solution to this is to set a static
clipId on your
For example, when creating a
VictoryLine component, you can pass a
<VictoryLinegroupComponent=<VictoryClipContainer clipId=1 />/>
clipId attached to your
VictoryLine component will always be the same, and your snapshot will not change with each test run.