Skip to content

Any plan to remove the dependency on vue-demi? #827

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
agarny opened this issue Apr 7, 2025 · 3 comments · May be fixed by #828
Open
1 task done

Any plan to remove the dependency on vue-demi? #827

agarny opened this issue Apr 7, 2025 · 3 comments · May be fixed by #828

Comments

@agarny
Copy link

agarny commented Apr 7, 2025

Confirmation

  • I can confirm this is a feature request for the Vue component instead of ECharts itself.

Details

Looking at vue-demi, I couldn't help but notice their notice that reads that vue-demi should not be used for new projects and will be deprecated in the future. I understand that vue-echarts is not a new project, but what about the day vue-demi is deprecated? In fact, is there still a need to support Vue 2 going forward?

@kingyue737
Copy link
Contributor

kingyue737 commented Apr 9, 2025

I share your view. VueUse has dropped vue-demi in v12, and Pinia has dropped vue-demi in v3.

Since ECharts v6 is planned to be released soon apache/echarts#19959 , IMO we could both end support of Vue 2 and upgrade ECharts to v6 in the next major release. Users who still want to use Vue-ECharts in Vue 2 can just stay on Vue-ECharts v7 which is very stable.

@Justineo
Copy link
Member

Justineo commented Apr 9, 2025

I looked into it, and it seems that ECharts 6 will be released in about a month or two. When that happens, I think we can go with the strategy @kingyue737 suggested—upgrade to ECharts 6 and drop Vue 2 support at the same time, and release vue-echarts@8.

@agarny
Copy link
Author

agarny commented Apr 9, 2025

Thanks @Justineo and @kingyue737, this seems like a good way forward.

@kingyue737 kingyue737 linked a pull request Apr 21, 2025 that will close this issue
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants