Skip to content
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

Migrate from Vue2 (vuetify2) to Vue3 (vuetify3) #1665

Closed
sbernard31 opened this issue Oct 25, 2024 · 5 comments
Closed

Migrate from Vue2 (vuetify2) to Vue3 (vuetify3) #1665

sbernard31 opened this issue Oct 25, 2024 · 5 comments
Labels
bsserver Impact LWM2M bootstrap server demo Impact our demo (not libraries) housekeeping Refactoring, cleaning code or API server Impact LWM2M server

Comments

@sbernard31
Copy link
Contributor

Vue 2 will reach End of Life (EOL) on December 31st, 2023.
HeroDevs’ NES (Never-Ending Support) for Vue 2 is a commercial (not open source) support so this is not a solution.

So we should probably move to vue3 !

Note that vuetify 2 is only compatible with vue2 and vuetify 3 is only compatible with vue3 (so both should be migrate together)
vite should works with both.

Migration will not be so easy I guess... 😞

This is part of : #1492

@sbernard31 sbernard31 added server Impact LWM2M server demo Impact our demo (not libraries) bsserver Impact LWM2M bootstrap server housekeeping Refactoring, cleaning code or API labels Oct 25, 2024
@sbernard31
Copy link
Contributor Author

sbernard31 commented Oct 25, 2024

Vue2 begin to be affected by "not fixed" vulnerability : https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-9506

In this is case, I understand we are not concerned but remind us that we should probably start to move forward on this topic.

About CVE-2024-9506, I'm not sure to see how this is really a vulnerability. This almost looks like as a way to frighten vue2 users and make them pay for HeroDev's for vue2.... see : https://herodevs.com/vulnerability-directory/cve-2024-6783

@sbernard31
Copy link
Contributor Author

I will try to work on that (my guess this will be painful)

But I think better to move forward on #1550 first.

@sbernard31
Copy link
Contributor Author

@sbernard31
Copy link
Contributor Author

I created a PR about that : #1679

@sbernard31
Copy link
Contributor Author

This is done but lot of changes was done so maybe there is some issue. (especially cosmetic ones)
Maybe I will take 1/2 or 1 days by weeks to try to improve this step by step.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bsserver Impact LWM2M bootstrap server demo Impact our demo (not libraries) housekeeping Refactoring, cleaning code or API server Impact LWM2M server
Projects
None yet
Development

No branches or pull requests

1 participant