## Goal Migrate all our pages to Vue 3. ## Why Vue 2 has been end-of-life since December 31, 2023, over 2.5 years without security patches. For our FedRAMP customers, running an unsupported framework is an active compliance risk that grows every month. Beyond security, our AI coding tools produce better suggestions against Vue 3 code, key libraries we need are Vue 3 only, and candidates consistently ask about our frontend stack during interviews. What does it bring for engineers. - Better AI-assisted development. Vue 3 is the default in all current documentation, tutorials, and community examples. AI coding tools (Duo and others) are trained predominantly on Vue 3 patterns, meaning suggestions for our Vue 2 codebase are frequently inaccurate or require manual correction. Migrating directly improves the quality of AI-generated code you work with every day. - Modern libraries. Vue 3 unlocks libraries that teams have been asking for, like vue-flow for workflow visualization, along with actively maintained versions of the tools we already depend on. - Better TypeScript support. Vue 3 was built with TypeScript from the ground up. Types are accurate and inference works properly. Moving to Vue 3 can open doors for TS in our codebase. ## How > New tooling makes this straightforward: you will need to add a feature flag, a YAML file per entrypoint, and smoke test your key workflows. > > The migration steps are here: https://docs.gitlab.com/development/fe_guide/vue3_migration/#option-1-recommended-migrate-your-page-entrypoint-using-a-feature-flag-and-vue3_migrationyml > > and if you want to see how migration MR looks, here is an example: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/247789 > Please assign your migration MRs to `@mrincon`, `@xanf`, or `@ntepluhina` for review. If you run into issues or have questions, please reach out in #vue3_migration. ## Progress dashboard https://vue3-migration-dashboard-0afc95.gitlab.io/