The end-of-life nobody scheduled time for

Vue is a popular framework for building the interactive parts of websites and web applications. If something your business depends on was built with Vue 2, it is now running on a version that reached the end of its life at the end of 2023. The application still works, which is why this rarely makes it onto anyone’s priority list — but Vue 2 no longer receives updates or security fixes, and moving to Vue 3 is more than the small step the version numbers imply.

Why Vue 3 is not a drop-in replacement

Vue 3 contains breaking changes that make it incompatible with Vue 2. It is a better framework — faster, with stronger support for building larger applications — but the improvements came at the cost of compatibility. An application written for Vue 2 will not simply run on Vue 3. It needs migration work, and the amount depends on how the application was built and how many other libraries it relies on, each of which has its own move to make.

For a small, self-contained interface, this is manageable. For a substantial application with many dependencies, it is a real piece of work that needs planning and budget — not something a developer fits in around other tasks.

Why so many applications are still on Vue 2

Vue 3 has been the default for years, yet a large number of applications are still on Vue 2. The reason is the familiar one: it works, so the migration keeps slipping. The difference now is that the support has actually ended. The grace period is over, and every month on Vue 2 is a month on an unmaintained framework.

What the risk looks like

An unmaintained framework will not be patched when a security issue is found. It will fall progressively out of step with the browsers and tools around it. And the libraries your application depends on will move on to Vue 3, leaving the Vue 2 versions frozen — so the application becomes harder to maintain and risky to change, even for routine work.

For a customer-facing application, or one that handles data of any sensitivity, this is a business risk dressed as a technical detail. The cost of addressing it only rises as the gap between Vue 2 and the current ecosystem widens.

The right way to approach it

The good news, compared with some of the harder end-of-life moves, is that Vue 2 to Vue 3 is a migration rather than a ground-up reinvention — there is a defined path, and it can often be done in stages. But “defined path” is not the same as “trivial,” and the dependencies are where the effort and the surprises live. The work needs to be sized honestly before it starts.

As with any forced move, it is also a moment to take stock: which parts of the application are actually used, what should be improved while you are in there, and whether the application still fits what the business needs. A migration done thoughtfully leaves you better off than you were. A migration done as a box-ticking exercise just resets the clock.

What to do now

Start with an assessment of the application and its dependencies, so you know the true size of the move and the safest sequence to make it in. That turns “we should probably move off Vue 2” into a planned, costed piece of work rather than an open-ended worry — and keeps it from becoming an emergency the day something breaks.

If an application you rely on is built on Vue 2, it is unsupported now, not at some future date. We will scope what moving it actually takes.

Start a Conversation