Working with Vue.js?

Vue 2 past end of life, or a Vue 3 upgrade that stalled? We finish it.

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.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

console

still failing

What it is

Vue.js at a glance

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.

Type
Front-end framework
First released
2014
License
MIT, free and permissive
Maintained by
Evan You and open source contributors
Typically used for
Single-page apps, admin dashboards, internal tooling, Nuxt-rendered marketing sites, progressive enhancement of server-rendered pages

The honest version

Vue.js pros and cons

No technology is all upside. This is where Vue.js earns its place and where it tends to cause trouble.

Where Vue.js is strong

  • A gentle learning curveA developer who knows HTML, CSS and a bit of JavaScript can be productive in a Single-File Component on the first afternoon, without serving a build of toolchain knowledge first.
  • Options or Composition, your pickTeams that like the familiar shape keep the Options API. Teams that want reusable logic lean on Composition and script setup. Both ship in the same framework.
  • Documentation that respects your timeThe official guide is thorough, written in plain English, and covers both APIs with real examples rather than toy ones.
  • Single-File Components are pleasant to work inTemplate, script and style sit in one .vue file with scoped CSS, so a component reads top to bottom instead of across four files.
  • Vite gives fast dev feedbackCold starts measured in seconds and HMR that preserves component state make the inner loop quick, which matters more than any benchmark number.
  • Pinia is a clean storeAfter years of Vuex boilerplate, Pinia drops the mutations layer, keeps full TypeScript inference, and feels like code you would write anyway.
  • Nuxt 3 is a strong SSR and SSG optionRouting, data fetching, server endpoints and build output all come wired up, which suits content sites and marketing pages that still need interactivity.
  • A strong ecosystem for admin and internal toolsElement Plus, Vuetify, PrimeVue and Naive UI cover most form-heavy and data-heavy screens without building a design system from scratch.

Where Vue.js bites

  • Vue 2 is past end of lifeVue 2 reached end of life on December 31, 2023 and a surprising number of production apps still run on it. The migration is not a flag-flip: Composition API, Vite migration, filter removal, event bus removal, Vuex to Pinia and Vue Router v4 breaking changes all land at once.
  • Ecosystem breakage between Vue 2 and Vue 3UI libraries from the Vue 2 era, Element UI and Vuetify 2 among them, have Vue 3 forks or successors with different names, APIs and props. Half of a migration is swapping components your screens depend on.
  • Options versus Composition splits teamsNew hires learned Composition first and want script setup everywhere; the people who built the app wrote Options and find the new shape harder to read. Code reviews stall on style rather than substance.
  • Nuxt 2 to Nuxt 3 is a rewrite in practiceNuxt 2 reached end of life in June 2024. The config, module API, server routes and data fetching all changed enough that moving an app across is closer to building a new one with your templates copied in.
  • TypeScript was retrofitted, not nativeVue 3 and script setup made types usable, but defineProps with withDefaults, generic components and provide/inject types still have sharp edges that catch out teams moving from a strict TypeScript backend.
  • Smaller hiring pool outside Asia and EuropeVue is huge in parts of the world and modest in others. In US hiring, candidates often have a line of Vue on their resume and five years of React under it, which is worth knowing before you staff a Vue rebuild.

Sound familiar?

Common Vue.js problems we fix

The Vue.js problems that bring people to us, and what you have once each one is fixed.

Vue 2 reached end of life December 31, 2023

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

SyntaxError: Unexpected token '?' (filters removed in Vue 3)

Vue 3 upgrade broke the templates

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

Nuxt 2 EOL June 2024

Nuxt 2 app past support

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

vuex store: mutation 'SET_USER' not registered

Vuex store going to Pinia

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

Composition API: provide/inject not reactive

Composition API conversion stalled

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

defineProps + withDefaults issue in script setup

TypeScript breaks under script setup

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

vue-router: NavigationDuplicated

Vue Router 4 breaking changes

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

last developer: contactable via LinkedIn

The agency that built it moved on

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

Vue.js help, from migration to upkeep

Ring us for a Vue 2 to 3 push, or let us own the whole front end over time.

Vue 2 to Vue 3
Filters, event bus and removed options worked through, Options kept where it earns its place, Composition where it helps, measured against the test suite at every step.
Nuxt 2 to Nuxt 3
Modules replaced, server routes rewritten against the new API, data fetching moved to useFetch and useAsyncData, with the same URLs on the other side.
Vuex to Pinia
Mutations retired, actions converted, types tightened. We do it store by store so the rest of the app does not have to change in step.
Composition API conversion
Options components moved to script setup where it pays off, reusable logic pulled into composables, reactivity handled properly across provide and inject.
Toolchain
Webpack to Vite, ESLint and Prettier set up for Vue 3, CI that catches the breaking changes before merge.
Managed Tech
Vue and Nuxt dependency updates tested in a preview build, bundle size tracked, security advisories triaged, and an engineer on call when a merge breaks preview.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Vue.js alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Vue.js questions

Something else? Call+1 737 727 7327

Can you upgrade our Vue 2 application to Vue 3?

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.

Should we migrate from Options API to Composition API?

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.

Can you take over a Vue codebase from a previous developer?

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.

Why did our Vue app break after we tried to upgrade dependencies?

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.

How do we move from Nuxt 2 to Nuxt 3?

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.

How much does Vue.js help cost?

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

Vue app giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.