-
Notifications
You must be signed in to change notification settings - Fork 266
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
Migration to Vue 3 #7653
Comments
First plugin discontinued since 5 years: https://github.com/fgr-araujo/vue-shortkey |
To do after upgrading to Vue 2.7: |
Since moving to Vue 3 will potentially introduce breakage into existing UI extensions that folks (internal & otherwise) have written, we need to warn people about that risk when we finally do ship this. |
This is going to break for sure something and since we still don't have enough core E2E tests and our real code coverage is 14% |
Closing as Vue3 branch merged. |
Description
Vue 2 is going to be EOM for the end of 2023. This issue is to track the required operation to reach from basic to optimal migration of Vue to version 3.
Context
Since it has been decided to remove Nuxt, due lack of SSR and given the SPA architecture is optimal for our case, it will be defined afterward the requirement to fulfill the migration list.
The goal is to make it possible to work with Vue 3, although reaching an ex novo state would facilitate the development and further integrations.
Requirements
Nuxt Removal
nuxt-link
withrouter-link
#10716Vue
First steps
Configuration
Epics to be completed before migration
Migration
Secondary
Extensions
As part of the migration, we'll have to update also the syntax for the extensions.
For these cases, we can use the script from #9541 and check all the crossed requirements to be at least mentioned for each extension.
Extras (non-blockers)
Issues to be checked if solved on migration
Optional
Test migration to Vitest?As Jest is ESM hell configuration and is embed in Vitest, this is going to be handled with Vite migrationThe text was updated successfully, but these errors were encountered: