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.
Optional chart init configurations. See echarts.init‘s opts parameter here →
Injection key: INIT_OPTIONS_KEY.
theme: string | object
Theme to be applied. See echarts.init‘s theme parameter here →
Injection key: THEME_KEY.
option: object
ECharts’ universal interface. Modifying this prop triggers Vue ECharts to compute an update plan and call setOption. Read more here →
Smart update
If you supply update-options (via prop or injection), Vue ECharts forwards it directly to setOption and skips the planner.
Manual setOption calls (only available when manual-update is true) 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 [] with replaceMerge, ID/anonymous deletions trigger replaceMerge, and risky changes fall back to notMerge: true.
update-options: object
Options for updating chart option. If supplied (or injected), Vue ECharts forwards it directly to setOption, skipping the smart update. See echartsInstance.setOption‘s opts parameter here →
Injection key: UPDATE_OPTIONS_KEY.
group: string
Group name to be used in chart connection. See echartsInstance.grouphere →
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. See echartsInstance.showLoading‘s opts parameter here →
Injection key: LOADING_OPTIONS_KEY.
manual-update: boolean (default: false)
Handy for performance-sensitive charts (large or high-frequency updates). When set to true, Vue only uses the option prop for the initial render; later prop changes do nothing and you must drive updates via setOption on a template ref. If the chart re-initializes (for example due to init-options changes, flipping manual-update, or a remount), the manual state is discarded and the chart is rendered again from the current option value.
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.
Event handlers passed via attrs are reactive by default. Updating onClick, onZr:*, or onNative:* handlers will rebind them automatically.
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);
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/csp is removed. Use vue-echarts instead. You only need to manually include vue-echarts/style.css if you are both enforcing a strict CSP that prevents inline <style> injection and targeting browsers that don’t support the CSSStyleSheet() constructor.
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.
Vue ECharts
Vue.js component for Apache ECharts™.
Installation & usage
npm
Example
Demo →
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
optioncode into the tool, and it will generate the exact import statements for you.Try it →
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 viawindow.VueECharts.Demo →
See more examples here.
Props
init-options: objectOptional chart init configurations. See
echarts.init‘soptsparameter here →Injection key:
INIT_OPTIONS_KEY.theme: string | objectTheme to be applied. See
echarts.init‘sthemeparameter here →Injection key:
THEME_KEY.option: objectECharts’ universal interface. Modifying this prop triggers Vue ECharts to compute an update plan and call
setOption. Read more here →Smart update
update-options(via prop or injection), Vue ECharts forwards it directly tosetOptionand skips the planner.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.null, removed arrays become[]withreplaceMerge, ID/anonymous deletions triggerreplaceMerge, and risky changes fall back tonotMerge: true.update-options: objectOptions for updating chart option. If supplied (or injected), Vue ECharts forwards it directly to
setOption, skipping the smart update. SeeechartsInstance.setOption‘soptsparameter here →Injection key:
UPDATE_OPTIONS_KEY.group: stringGroup name to be used in chart connection. See
echartsInstance.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: objectConfiguration item of loading animation. See
echartsInstance.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 to
true, 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-ondirective.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→click→dblclick→mouseover→mouseout→mousemove→mousedown→mouseup→globalout→contextmenu→zr:clickzr:mousedownzr:mouseupzr:mousewheelzr:dblclickzr:contextmenuSee 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.Event handlers passed via attrs are reactive by default. Updating
onClick,onZr:*, oronNative:*handlers will rebind them automatically.Provide / inject
Vue ECharts provides provide/inject API for
theme,init-options,update-optionsandloading-optionsto help configuring contextual options. eg. forthemeyou can use the provide API like this:Composition API
Options API
Methods
setOption→getWidth→getHeight→getDom→getOption→resize→dispatchAction→convertToPixel→convertFromPixel→containPixel→getDataURL→getConnectedDataURL→clear→dispose→Slots
Vue ECharts supports three slot categories:
tooltip.formatter.toolbox.feature.dataView.optionToContent.#graphicslot (enabled by importingvue-echarts/graphic) for buildingoption.graphicdeclaratively withG*components.Callback slot naming convention (
tooltip*/dataView*)These naming rules apply to callback slots only. The graphic slot name is always
#graphic.tooltip/dataView, followed by hyphen-separated path segments to the target.optionproperty name or an array index (for arrays, use the numeric index).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.optionToContentThe slot props correspond to the first parameter of the callback function.
Usage
Example →
Graphic slot
Available components:
GGroupGRectGCircleGTextGLineGPolylineGPolygonGImageGSectorGRingGArcGBezierCurveGCompoundPathRead more at ECharts
option.graphic→Usage
Static methods
Static methods can be accessed from
echartsitself.CSP:
style-srcorstyle-src-elemIf 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 includevue-echarts/style.css.Migration to v8
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
classsupport. 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 theCSSStyleSheet()constructor.Local development
Open
http://localhost:5173to 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.