GitHub - ecomfe/vue-echarts: Vue.js component for Apache ECharts™. (original) (raw)
Vue ECharts
Vue.js component for Apache ECharts™.
Still using Vue 2? Read v7 docs here →
Installation & usage
npm
npm install echarts vue-echarts
Example
On-demand importing 
To keep your bundle size small, we recommend manually importing the components and charts you need from ECharts. To make this easier, we’ve created an import code generator. Simply paste your option code into the tool, and it will generate the exact import statements for you.
But if you really want to import the whole ECharts bundle without having to import modules manually, just add this in your code:
CDN
Drop <script> inside your HTML file and access the component via window.VueECharts.
const app = Vue.createApp(...)
// register globally (or you can do it locally) app.component('VChart', VueECharts)
See more examples here.
Props
init-options: object
Optional chart init configurations. Seeecharts.init'soptsparameter here →
Injection key:INIT_OPTIONS_KEY.theme: string | object
Theme to be applied. Seeecharts.init'sthemeparameter here →
Injection key:THEME_KEY.option: object
ECharts' universal interface. Modifying this prop triggers Vue ECharts to compute an update plan and callsetOption. Read more here →
Smart update
- If you supply
update-options(via prop or injection), Vue ECharts forwards it directly tosetOptionand skips the planner. - Manual
setOptioncalls (only available whenmanual-updateistrue) behave like native ECharts, honouring only the per-call override you pass in and are not carried across re-initializations. - Otherwise, Vue ECharts analyses the change: removed objects become
null, removed arrays become[]withreplaceMerge, ID/anonymous deletions triggerreplaceMerge, and risky changes fall back tonotMerge: true. update-options: object
Options for updating chart option. If supplied (or injected), Vue ECharts forwards it directly tosetOption, skipping the smart update. SeeechartsInstance.setOption'soptsparameter here →
Injection key:UPDATE_OPTIONS_KEY.group: string
Group name to be used in chart connection. SeeechartsInstance.grouphere →autoresize: boolean | { throttle?: number, onResize?: () => void }(default:false)
Whether the chart should be resized automatically whenever its root is resized. Use the options object to specify a custom throttle delay (in milliseconds) and/or an extra resize callback function.loading: boolean(default:false)
Whether the chart is in loading state.loading-options: object
Configuration item of loading animation. SeeechartsInstance.showLoading'soptsparameter here →
Injection key:LOADING_OPTIONS_KEY.manual-update: boolean(default:false)
Handy for performance-sensitive charts (large or high-frequency updates). When set totrue, Vue only uses theoptionprop for the initial render; later prop changes do nothing and you must drive updates viasetOptionon a template ref. If the chart re-initializes (for example due toinit-optionschanges, flippingmanual-update, or a remount), the manual state is discarded and the chart is rendered again from the currentoptionvalue.
Events
You can bind events with Vue's v-on directive.
Note
Only the .once event modifier is supported as other modifiers are tightly coupled with the DOM event system.
Vue ECharts support the following events:
highlight→downplay→selectchanged→legendselectchanged→legendselected→legendunselected→legendselectall→legendinverseselect→legendscroll→datazoom→datarangeselected→timelinechanged→timelineplaychanged→restore→dataviewchanged→magictypechanged→geoselectchanged→geoselected→geounselected→axisareaselected→brush→brushEnd→brushselected→globalcursortaken→rendered→finished→- Mouse events
- ZRender events
zr:clickzr:mousedownzr:mouseupzr:mousewheelzr:dblclickzr:contextmenu
See supported events in the ECharts API reference →
Native DOM events
As Vue ECharts binds events to the ECharts instance by default, there is some caveat when using native DOM events. You need to prefix the event name with native: to bind native DOM events.
Provide / inject
Vue ECharts provides provide/inject API for theme, init-options, update-options and loading-options to help configuring contextual options. eg. for theme you can use the provide API like this:
Composition API
import { THEME_KEY } from "vue-echarts"; import { provide } from "vue";
provide(THEME_KEY, "dark");
// or provide a ref const theme = ref("dark"); provide(THEME_KEY, theme);
// getter is also supported provide(THEME_KEY, () => theme.value);
Options API
import { THEME_KEY } from 'vue-echarts' import { computed } from 'vue'
export default { { provide: { [THEME_KEY]: 'dark' } } }
// Or make injections reactive export default { data() { return { theme: 'dark' } }, provide() { return { [THEME_KEY]: computed(() => this.theme) } } }
Methods
setOption→getWidth→getHeight→getDom→getOption→resize→dispatchAction→convertToPixel→convertFromPixel→containPixel→getDataURL→getConnectedDataURL→clear→dispose→
Note
The following ECharts instance methods aren't exposed because their functionality is already provided by component props:
- showLoading / hideLoading: use the
loadingandloading-optionsprops instead. - setTheme: use the
themeprop instead.
Slots 
Vue ECharts allows you to define ECharts option's tooltip.formatter and toolbox.feature.dataView.optionToContent callbacks via Vue slots instead of defining them in your option object. This simplifies custom HTMLElement rendering using familiar Vue templating.
Slot naming convention
- Slot names begin with
tooltip/dataView, followed by hyphen-separated path segments to the target. - Each segment corresponds to an
optionproperty name or an array index (for arrays, use the numeric index). - The constructed slot name maps directly to the nested callback it overrides.
Example mappings:
tooltip→option.tooltip.formattertooltip-baseOption→option.baseOption.tooltip.formattertooltip-xAxis-1→option.xAxis[1].tooltip.formattertooltip-series-2-data-4→option.series[2].data[4].tooltip.formatterdataView→option.toolbox.feature.dataView.optionToContentdataView-media-1-option→option.media[1].option.toolbox.feature.dataView.optionToContent
The slot props correspond to the first parameter of the callback function.
Usage
<!-- Tooltip on xAxis -->
<template #tooltip-xAxis="params">
<div>X-Axis : {{ params.value }}</div>
</template>
<!-- Data View Content -->
<template #dataView="option">
<table>
<thead>
<tr>
<th v-for="(t, i) in option.dataset[0].source[0]" :key="i">
{{ t }}
</th>
</tr>
</thead>
<tbody>
<tr v-for="(row, i) in option.dataset[0].source.slice(1)" :key="i">
<th>{{ row[0] }}</th>
<td v-for="(v, i) in row.slice(1)" :key="i">{{ v }}</td>
</tr>
</tbody>
</table>
</template>
Note
Slots take precedence over the corresponding callback defined in props.option.
Static methods
Static methods can be accessed from echarts itself.
CSP: style-src or style-src-elem
If you are both enforcing a strict CSP that prevents inline <style> injection and targeting browsers that don't support the CSSStyleSheet() constructor, you need to manually include vue-echarts/style.css.
Migration to v8
Note
Please make sure to read the upgrade guide for ECharts 6 as well.
The following breaking changes are introduced in vue-echarts@8:
- Vue 2 support is dropped: If you still need to stay on Vue 2, use vue-echarts@7.
- Browser compatibility changes: We no longer provide compatibility for browsers without native class support. If you need to support legacy browsers, you must transpile the code to ES5 yourself.
- CSP entry point removed: The entry point
vue-echarts/cspis removed. Usevue-echartsinstead. You only need to manually includevue-echarts/style.cssif you are both enforcing a strict CSP that prevents inline<style>injection and targeting browsers that don't support the CSSStyleSheet() constructor.
Local development
Open http://localhost:5173 to see the demo.
For testing and CI details, see tests/TESTING.md.
Notice
The Apache Software Foundation Apache ECharts, ECharts, Apache, the Apache feather, and the Apache ECharts project logo are either registered trademarks or trademarks of the Apache Software Foundation.