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
npm install --save @reactchartjs/react-chart.js chart.js
# or
yarn add @reactchartjs/react-chart.js chart.js
chart.js ^2.5.0
import { Doughnut } from '@reactchartjs/react-chart.js';
<Doughnut data={...} />
Live: jerairrest.github.io/react-chart.js
See these examples for more information
id?: string;
height?: number;
width?: number;
redraw?: boolean;
type: Chart.ChartType
data: Chart.ChartData | (canvas: HTMLCanvasElement | null) => Chart.ChartData;
options?: Chart.ChartOptions;
plugins?: Chart.PluginServiceRegistrationOptions[];
getDatasetAtEvent?: (dataset: Array<{}>, event: React.MouseEvent<HTMLCanvasElement>) => void;
getElementAtEvent?: (element: [{}], event: React.MouseEvent<HTMLCanvasElement>) => void;
getElementsAtEvent?: (elements: Array<{}>, event: React.MouseEvent<HTMLCanvasElement>) => void;
Type string
Default: undefined
ID attribute applied to the rendered canvas
Type: number
Default: 150
Height attribute applied to the rendered canvas
Type: number
Default: 300
Width attribute applied to the rendered canvas
Type: boolean
Default: false
If true, will tear down and redraw chart on all updates
Type: 'line' | 'bar' | 'horizontalBar' | 'radar' | 'doughnut' | 'polarArea' | 'bubble' | 'pie' | 'scatter'
Chart.js chart type (required only on ChartComponent)
Type: Chart.ChartData | (canvas: HTMLCanvasElement | null) => Chart.ChartData
The data object that is passed into the Chart.js chart (more info).
This can also be a function, that receives a canvas element and returns the data object.
const data = canvas => {
const ctx = canvas.getContext('2d');
const g = ctx.createLinearGradient(...);
return {
datasets: [{
backgroundColor: g,
// ...the rest
}],
};
}
Type: Chart.ChartOptions
The options object that is passed into the Chart.js chart (more info)
Type: Chart.PluginServiceRegistrationOptions[]
The plugins array that is passed into the Chart.js chart (more info)
Type: (dataset: Array<{}>, event: React.MouseEvent<HTMLCanvasElement>) => void
Default: undefined
Proxy for Chart.js getDatasetAtEvent
. Calls with dataset and triggering event
Type: (element: [{}], event: React.MouseEvent<HTMLCanvasElement>) => void
Default: undefined
Proxy for Chart.js getElementAtEvent
. Calls with single element array and triggering event
Type: (elements: Array<{}>, event: React.MouseEvent<HTMLCanvasElement>) => void
Default: undefined
Proxy for Chart.js getElementsAtEvent
. Calls with element array and triggering event
In order for Chart.js to obey the custom size you need to set maintainAspectRatio
to false
<Bar
data={data}
width={100}
height={50}
options={{ maintainAspectRatio: false }}
/>
The Chart.js instance can be accessed by placing a ref to the element as:
const App => {
const ref = useRef();
return <Doughnut ref={ref} data={data} options={options} />;
};
The canvas node and hence context can be accessed within the data 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
// ...the rest
}
}
return <Line data={data} />;
}
Chart.js defaults can be set by importing the defaults
object:
import { defaults } from '@reactchartjs/react-chart.js';
// 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 '@reactchartjs/react-chart.js';
import merge from 'lodash.merge';
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 '@reactchartjs/react-chart.js';
componentWillMount() {
Chart.pluginService.register({
afterDraw: function (chart, easing) {
// Plugin code.
}
});
}
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.NOTE: The source code for the component is in src
. A transpiled CommonJS version (generated with Babel) is available in dist
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.
MIT Licensed Copyright (c) 2020 Jeremy Ayerst
FAQs
react-chartjs-2
The npm package @reactchartjs/react-chart.js receives a total of 0 weekly downloads. As such, @reactchartjs/react-chart.js popularity was classified as not popular.
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.