npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.


Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2021 – Pkg Stats / Ryan Hefner








build status version downloads license

Looking for maintainers!!


React wrapper for Chart.js 2 Open for PRs and contributions!

UPDATE to 2.x

As of 2.x we have made chart.js a peer dependency for greater flexibility. Please add chart.js as a dependency on your project to use 2.x. Currently, 2.5.x is the recommended version of chart.js to use.

Demo & Examples

Live demo:

To build the examples locally, run:

npm install
npm start

Then open localhost:8000 in a browser.

Demo & Examples via React Storybook

We have to build the package, then you can run storybook.

npm run build
npm run storybook

Then open localhost:6006 in a browser.

Installation via NPM

npm install --save react-chartjs-2 chart.js

Installation via YARN

yarn add react-chartjs-2 chart.js


Check example/src/components/* for usage.

import { Doughnut } from 'react-chartjs-2';

<Doughnut data={...} />


  • data: (PropTypes.object | PropTypes.func).isRequired,
  • width: PropTypes.number,
  • height: PropTypes.number,
  • id: PropTypes.string,
  • legend: PropTypes.object,
  • options: PropTypes.object,
  • redraw: PropTypes.bool,
  • getDatasetAtEvent: PropTypes.func,
  • getElementAtEvent: PropTypes.func,
  • getElementsAtEvent: PropTypes.func
  • onElementsClick: PropTypes.func, // alias for getElementsAtEvent (backward compatibility)

Custom size

In order for Chart.js to obey the custom size you need to set maintainAspectRatio to false, example:

  options={{ maintainAspectRatio: false }}

Chart.js instance

Chart.js instance can be accessed by placing a ref to the element as:

class MyComponent extends React.Component {
  constructor(props) {
    this.chartReference = React.createRef();

  componentDidMount() {
    console.log(this.chartReference); // returns a Chart.js instance reference

  render() {
    return (<Doughnut ref={this.chartReference} data={data} options={options} />)

Getting context for data generation

Canvas node and hence context, that can be used to create CanvasGradient background, is passed as argument to data if given as function:

This approach is useful when you want to keep your components pure.

render() {
  const data = (canvas) => {
    const ctx = canvas.getContext("2d")
    const gradient = ctx.createLinearGradient(0,0,100,0);
    return {
      backgroundColor: gradient

  return (<Line data={data} />)

Chart.js Defaults

Chart.js defaults can be set by importing the defaults object:

import { defaults } from 'react-chartjs-2';

// Disable animating charts by default. = false;

If you want to bulk set properties, try using the lodash.merge function. This function will do a deep recursive merge preserving previously set values that you don't want to update.

import { defaults } from 'react-chartjs-2';
import merge from 'lodash.merge';
// or
// import { merge } from 'lodash';

merge(defaults, {
  global: {
    animation: false,
    line: {
      borderColor: '#F85F73',

Chart.js object

You can access the internal Chart.js object to register plugins or extend charts like this:

import { Chart } from 'react-chartjs-2';

componentWillMount() {
    afterDraw: function (chart, easing) {
      // Plugin code.

Scatter Charts

If you're using Chart.js 2.6 and below, add the showLines: false property to your chart options. This was later added in the default config, so users of later versions would not need to do this extra step.


onElementsClick || getElementsAtEvent (function)

A function to be called when mouse clicked on chart elememts, will return all element at that point as an array. Check

  onElementsClick: (elems) => {},
  getElementsAtEvent: (elems) => {},
  // `elems` is an array of chartElements

getElementAtEvent (function)

Calling getElementAtEvent(event) on your Chart instance passing an argument of an event, or jQuery event, will return the single element at the event position. If there are multiple items within range, only the first is returned Check

  getElementAtEvent: (elems) => {},
  // => returns the first element at the event point.

getDatasetAtEvent (function)

Looks for the element under the event point, then returns all elements from that dataset. This is used internally for 'dataset' mode highlighting Check

  getDatasetAtEvent: (dataset) => {}
  // `dataset` is an array of chartElements

Working with Multiple Datasets

You will find that any event which causes the chart to re-render, such as hover tooltips, etc., will cause the first dataset to be copied over to other datasets, causing your lines and bars to merge together. This is because to track changes in the dataset series, the library needs a key to be specified - if none is found, it can't tell the difference between the datasets while updating. To get around this issue, you can take these two approaches:

  1. Add a label property on each dataset. By default, this library uses the label property as the key to distinguish datasets.
  2. Specify a different property to be used as a key by passing a datasetKeyProvider prop to your chart component, which would return a unique string value for each dataset.

Development (src, lib and the build process)

NOTE: The source code for the component is in src. A transpiled CommonJS version (generated with Babel) is available in lib for use with node.js, browserify and webpack. A UMD bundle is also built to dist, which can be included without the need for any build system.

To build, watch and serve the examples (which will also watch the component source), run npm start. If you just want to watch changes to src and rebuild lib, run npm run watch (this is useful if you are working with npm link).


MIT Licensed Copyright (c) 2017 Jeremy Ayerst