ecomfe/vue-echarts — 10.7k★ on GitHub (TypeScript). Vue.js component for Apache ECharts™.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
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.
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:
import "echarts";
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. 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.group here →
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.
[!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
click →
dblclick →
mouseover →
mouseout →
mousemove →
mousedown →
mouseup →
globalout →
contextmenu →
ZRender events
zr:click
zr:mousedown
zr:mouseup
zr:mousewheel
zr:dblclick
zr: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.
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);
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/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.
Local development
pnpm i
pnpm dev
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.
The most recent commit recorded on ecomfe/vue-echarts was 3 days ago, based on the GitHub push timestamp. The repository has 1.5k forks — one of the better signals of community interest.
How many stars does ecomfe/vue-echarts have?
ecomfe/vue-echarts has 10.7k GitHub stars — refresh the page for the live number, or check github.com/ecomfe/vue-echarts. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
What language is ecomfe/vue-echarts written in?
ecomfe/vue-echarts is written primarily in TypeScript. GitHub's language field is based on the largest share of bytes in the default branch.
What license does ecomfe/vue-echarts use?
ecomfe/vue-echarts is released under the MIT license. Always verify the LICENSE file directly on GitHub for the authoritative terms — license strings can be edited out of sync with a project's actual stance.
What topics is ecomfe/vue-echarts associated with?
GitHub's repository topics for ecomfe/vue-echarts: "echarts", "vue", "vue-echarts". TopGit's editorial category is Frontend.
Where can I see ecomfe/vue-echarts in action?
The project maintains a homepage at https://vue-echarts.dev. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about ecomfe/vue-echarts?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/ecomfe/vue-echarts is the definitive source.