What we do
Tools
Industries
Department
How we workLet's talk →
Home/Hire Vue.js Developers to Get Off Vue 2
Vue.js Development

Hire Vue.js Developers for an App That Missed the Vue 3 Move

Vue 2 stopped getting fixes on December 31, 2023, security ones included. Plenty of Vue apps are still on it, because the developer who built them left before the migration started. If that's your app, the first job isn't new features. It's finding out how far behind it really is.

How far behind is your Vue app? Check these files

You don't need to read the code. Open the project and look for these. Each one you find is a piece of the migration.

  • package.json lists "vue": "^2..."

    That's the clearest sign. If it says 2.7, you're on the last Vue 2 release, which already has the Composition API and makes the move easier.

  • The scripts call vue-cli-service

    The app is built with Vue CLI, which is in maintenance mode. New Vue projects use Vite, and the build setup usually moves as part of the upgrade.

  • main.js starts with new Vue(...)

    Vue 3 apps start with createApp(). Global plugins, mixins and components registered on Vue itself all need moving.

  • Templates use filters, like {{ price | currency }}

    Filters were removed in Vue 3. Each one becomes a method or a computed value. There are usually more than anyone expects.

  • Components talk through an event bus ($on, $emit on a shared Vue instance)

    $on, $off and $once are gone in Vue 3. Anything that relied on a global bus needs another way to pass messages.

  • A UI kit like Vuetify 2 or Element UI

    These have separate Vue 3 versions (Vuetify 3, Element Plus) with changed components. On many apps this is the biggest single piece of work.

  • nuxt.config.js with "nuxt": "^2..."

    Nuxt 2 also reached end of life, in 2024. Moving to current Nuxt changes the server, the data fetching and the module list, so plan it as its own step.

Port to Vue 3, or keep Vue 2 alive a while longer?

Stay on Vue 2 for now

When the app is near the end of its life

  • It's an internal tool you plan to replace within a year or so.
  • Vue's own site points to paid extended support from HeroDevs for teams that need security fixes while they wait.
  • Freeze the dependencies, and don't add features that make the later move bigger.
Port to Vue 3

When the app is staying

  • Customers or staff use it daily and it keeps getting new features.
  • Packages you need have dropped Vue 2 support, so every update is a fight.
  • Browser changes or security fixes now land only in Vue 3.

For an app that's sticking around, extended support buys time, not a way out. The port gets more expensive with every feature added on Vue 2.

The order a Vue 2 to Vue 3 move runs in

Done in this order, the app keeps shipping while it moves. Done all at once, it usually becomes a rewrite.

  1. 1

    Get to Vue 2.7 first

    2.7 is still Vue 2, but it supports the Composition API and script setup. New and touched components can be written the Vue 3 way before anything else changes.

  2. 2

    Swap the build tool

    Move from Vue CLI or an old webpack setup to Vite. Builds get faster and the later steps get easier to test, but environment variables and import paths need checking.

  3. 3

    Switch to Vue 3 on the migration build

    The official compatibility build, @vue/compat, runs most Vue 2 code on Vue 3 and logs a warning for each old pattern. The team works through the warnings one by one instead of guessing.

    Watch for: the UI kit and other plugins. The compat build covers Vue itself, not third-party libraries, so those get upgraded or replaced here.

  4. 4

    Move the store

    Vuex still works on Vue 3, so this step can wait. Pinia is now the recommended store, and moving to it module by module makes the code easier to type and test.

  5. 5

    Remove the compat build

    Once the warnings are gone, drop @vue/compat and run on plain Vue 3. Test the flows people actually use, against the real backend.

Vue that talks to the rest of the business

A Vue app written by someone who was really thinking in React shows it: watchers doing the job of computed values, state passed around by hand, components that fight the reactivity system. Most of the Vue work that reaches n-frames is an interface tied to a backend or a third-party API that keeps changing underneath it. We build or connect that backend in the same project, so the front end and the data it shows don't drift apart.

If you're here looking for a Vue job, this isn't a listings page: n-frames is an agency that takes on Vue and Nuxt projects. If you're still choosing a framework, the React developer and Angular developer pages cover those, and frontend developer and JavaScript developer cover work that isn't tied to one framework.

Let's talk

Your Vue app on Vue 3, still shipping while it moves

n-frames moves Vue 2 and Nuxt 2 apps to current versions in stages, builds new Vue front ends, and connects them to the backends and APIs they depend on. You get a quote from someone who has opened your package.json, not a guess from a job post.

Quote the Vue 3 port →

Questions people ask

Is it harder to find help for a Vue project than a React one?

Usually, yes. Fewer developers specialize in Vue, so replacing one takes longer, and some who list it write it the way they'd write React. Ask to see Vue code they've written, ideally something on Vue 3 with the Composition API.

Our app is still on Vue 2. Does that matter?

Yes. Vue 2 reached end of life on December 31, 2023 and no longer gets security or browser fixes, and more packages drop Vue 2 support every year. How big the move is depends on the checks above: a 2.7 app with no filters or event bus is a far smaller job than a Vue 2.5 app on Vuetify 2.

Do you handle the backend too, or just the Vue front end?

Both, when the project needs it. Much of the Vue work we take on is wired to a backend or a third-party system, and we build or connect that side in the same engagement, so nobody has to coordinate two teams.

Is the Vue 3 migration quote really free, with no obligation?

Yes. The quote starts from your package.json and the checks above: Vue version, UI kit, filters, Nuxt. It prices the port in the stages shown. No charge, nothing to sign.

Can you move a Nuxt 2 site to the current Nuxt?

Yes. It's treated as its own step because data fetching, the server and most modules change. We keep the existing URLs working so search traffic isn't lost.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.