Research
Security News
Threat Actor Exposes Playbook for Exploiting npm to Build Blockchain-Powered Botnets
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
@reactchartjs/react-chart.js
Advanced tools
React wrapper for Chart.js 2 Open for PRs and contributions!
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.
Live demo: reactchartjs.github.io/react-chartjs-2
To build the examples locally, run:
npm install
npm start
Then open localhost:8000
in a browser.
We have to build the package, then you can run storybook.
npm run build
npm run storybook
Then open localhost:6006
in a browser.
npm install --save react-chartjs-2 chart.js
yarn add react-chartjs-2 chart.js
Check example/src/components/* for usage.
import { Doughnut } from 'react-chartjs-2';
<Doughnut data={...} />
In order for Chart.js to obey the custom size you need to set maintainAspectRatio
to false, example:
<Bar
data={data}
width={100}
height={50}
options={{ maintainAspectRatio: false }}
/>
Chart.js instance can be accessed by placing a ref to the element as:
class MyComponent extends React.Component {
constructor(props) {
super(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} />)
}
}
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 can be set by importing the defaults
object:
import { defaults } from 'react-chartjs-2';
// Disable animating charts by default.
defaults.global.animation = 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',
},
},
});
You can access the internal Chart.js object to register plugins or extend charts like this:
import { Chart } from 'react-chartjs-2';
componentWillMount() {
Chart.pluginService.register({
afterDraw: function (chart, easing) {
// Plugin code.
}
});
}
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.
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
}
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.
}
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
}
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:
label
property on each dataset. By default, this library uses the label
property as the key to distinguish datasets.datasetKeyProvider
prop to your chart component, which would return a unique string value for each dataset.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
FAQs
react-chartjs-2
We found that @reactchartjs/react-chart.js demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.