The app is still on Vue 2
No more security fixes, dependencies refusing to install, and every attempt to upgrade stalls on a UI library or a filter that Vue 3 no longer supports.
Running on Vue 3 with tests green
Working with Vue.js?
Most Vue apps that reach us were built on Vue 2 by a team that has since moved on, and the Vue 3 upgrade has been quoted twice and attempted once. We work through the breaking changes in order, swap the libraries that no longer have a Vue 3 release, and get the app onto a supported line without a ground-up rewrite.
What it is
Vue.js is a progressive JavaScript framework for building user interfaces, created by Evan You in 2014 after he worked on AngularJS at Google and wanted something lighter. It scales from a sprinkle of reactivity on a plain HTML page to a full single-page app with Vue Router, Pinia for state (or legacy Vuex), and server-side rendering through Nuxt.
Vue 2 was the long-standing line from 2016 to 2023 and still powers a lot of production code. Vue 3, released in 2020, introduced the Composition API, better TypeScript inference, a smaller runtime and real performance improvements. Vue 2 reached end of life on December 31, 2023, which is why most of the inbound work is now migrations.
The honest version
No technology is all upside. This is where Vue.js earns its place and where it tends to cause trouble.
Sound familiar?
The Vue.js problems that bring people to us, and what you have once each one is fixed.
No more security fixes, dependencies refusing to install, and every attempt to upgrade stalls on a UI library or a filter that Vue 3 no longer supports.
Running on Vue 3 with tests green
Filters, the global event bus and a handful of removed options are still in the code. The build passes locally and the pages crash in production.
Templates updated, no removed features
Content site on Nuxt 2 with modules that have no Nuxt 3 equivalent, server middleware written against the old API, and nobody willing to quote the rewrite.
Running on Nuxt 3 with the same URLs
A store full of modules, mutations and actions that nobody reads any more, mixed with a half-finished Pinia migration someone started on a Friday.
One store layer, typed end to end
Components converted to script setup but still passing refs through provide/inject without reactivity, so child components see stale values.
Reactivity working across the tree
Generic components, prop defaults and emits all compiled on Vue 2 with vue-class-component and fight back under script setup with strict TypeScript.
Types clean, no any left behind
Router guards written for v3, programmatic navigation that no longer rejects the same way, and dynamic routes that moved from path-to-regexp to the new matcher.
Routing on v4, guards behaving
A Vue codebase handed over with no docs, a .env file missing half its keys, and a build that only works on one laptop.
Buildable from a fresh clone
What we do
Ring us for a Vue 2 to 3 push, or let us own the whole front end over time.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes. Vue 2 reached end of life on December 31, 2023, so this is the most common job we take on. We work through filter removal, the event bus going away, Vue Router v4, Vuex to Pinia if you want it, and the UI library swap in order on a branch, rehearse the whole thing against your test suite, and only merge when the real screens pass too.
Not always, and rarely all at once. Options still works in Vue 3 and reads fine for straightforward components. Composition and script setup pay off where you have reusable logic across components or complicated reactivity to tame. We usually convert the parts that benefit and leave the rest alone.
Yes. We make the build reproducible from a fresh clone first, document the parts that are not obvious, then work through the backlog in priority order. You keep the code either way.
Usually a UI library that released a Vue 3 version under a new name with different component APIs, or a router update that changed how navigation guards reject. We work out which upgrade pulled in the breaking change, pin what needs pinning, and port the rest properly rather than rolling everything back.
In practice it is closer to a rewrite than an upgrade, because modules, server routes and data fetching all changed. We port page by page, keep the URLs the same so SEO does not suffer, and run both versions side by side on a staging host until the new one passes. Nuxt 2 hit end of life in June 2024, so putting this off gets more expensive, not less.
Estimates are free. Hand us the repo URL or a copy of package.json and the vue.config, and we come back with a scope before any code is touched.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: