Nuxt development

Build SEO-friendly, performantVue applications with Nuxt.js

Nuxt adds server rendering, file-based routing and a server layer to Vue. We use it where Vue pages must load quickly and rank in search. If you are on Nuxt 2 or 3, neither version now gets security patches, so an upgrade should be on your plan.

Discuss your Nuxt projectSee Vue development

What Nuxt work covers

Choosing how each route renders is the main design decision in a Nuxt project.

  • Public sites that must rank

    Marketing and content pages rendered on the server or pre-built, so that search engines and first-time visitors get complete HTML.

  • Hybrid applications

    Route rules allow a static marketing section and a logged-in dashboard to live in one project, each rendered in the way that suits it.

  • Upgrades from Nuxt 3

    Running the official codemods, moving to the app/ directory if you want it, and testing the data-fetching changes that the codemods can't judge.

  • Upgrades from Nuxt 2

    Effectively a Vue 2 to Vue 3 migration plus a framework change, with Vuex, modules and plugins all needing attention. We plan this one as a project in its own right.

Nuxt versions, as of October 2026

From the Nuxt roadmap and upgrade guide. Check this before anything else.

  • Nuxt 4 is current

    Stable since 16 July 2025, with 4.6.3 the latest on npm. It requires Node.js 22.22.3, 24.15 or 26 and newer, so older hosting may have to change.

  • Nuxt 3 ended on 31 July 2026

    Nuxt's roadmap says it no longer receives bug fixes or security patches. Nuxt 2 ended on 30 June 2024. Either way, a running site is on unsupported code.

  • Nuxt 5 is on the way

    Scheduled for an estimated Q4 2026, and still in development when we checked. Nuxt 4 is supported until six months after 5 is released, so 4 is the right target today.

What the upgrades really change

The code that breaks is rarely the code people expect.

  • Data fetching in Nuxt 4

    data from useAsyncData and useFetch is now a shallowRef, data and error default to undefined rather than null, and calls sharing a key share their state. Code that mutates nested data needs checking.

  • The app/ directory

    Nuxt 4 defaults its source directory to app/. The move is optional, because Nuxt detects the old layout and srcDir can be set explicitly.

  • Preparing for Nuxt 5

    Setting future.compatibilityVersion to 5 turns on many coming changes now, including case-sensitive routing and the Vite Environment API. It is a cheap way to find out what will break.

  • Not everything has a flag

    Nuxt 5 also moves to Nitro v3, which no flag enables, so custom server code deserves a look. Check older components too, since the Options API gets compiled out of the client bundle.

How a Nuxt upgrade runs

New builds start at the third step, once rendering modes have been chosen.

  1. Inventory modules and server code

    Each Nuxt module is checked for a compatible release, and we read everything in your server directory.

  2. Upgrade on a branch

    We run the pinned codemod recipe, then deal by hand with what it leaves behind, and keep the changes small enough to review.

  3. Compare rendered pages

    We compare the HTML, titles and canonicals of key routes before and after, because a rendering change can quietly affect search.

  4. Release and watch

    We check logs, Core Web Vitals and Search Console after launch, and keep the previous build ready to restore.

Ways to run Nuxt work

Small Nuxt 3 sites and large Nuxt 2 ones are very different jobs.

An upgrade from 3 to 4 can often be a fixed job once we have seen the module list, while a Nuxt 2 project is better split into stages. If you need a developer for longer, we can add one to your team, and hourly work starts from $20/h in USD, invoiced in USD, GBP, EUR or INR.

We are an engineering team in India with 3–5 hours of overlap with the UK and Europe; US calls by appointment. In the shared hours, a release can be checked by both teams. For the choice between frameworks, compare this with our Next.js page. The two solve similar problems for Vue and React.

Why this page doesn't name Nuxt sites

Most of our work is delivered under NDA, so many projects cannot be named.

Accordingly, we describe the upgrade route instead of naming sites. If you send a link to your own Nuxt site, we can often tell you which version it runs and what comes next.

Questions about Nuxt

Most are about versions and timing at the moment.

We are on Nuxt 3. How urgent is it?
Your site still works, but since 31 July 2026 it no longer gets security patches from the Nuxt project. We would plan the move to Nuxt 4 now, particularly if the site handles logins or personal data.
Should we wait for Nuxt 5?
No. Move to Nuxt 4 first, because that is the supported version. Then you can turn on the Nuxt 5 compatibility flag and find problems ahead of the actual upgrade.
Nuxt or Next.js?
If your team writes Vue, use Nuxt. If it writes React, use Next.js. They solve the same problem, so existing skills and libraries matter more than feature differences.
Can Nuxt run on our existing server?
Pre-rendered pages can be hosted almost anywhere. Server rendering needs a Node.js process or a supported platform, and the version must meet Nuxt 4's Node.js requirement, so we check that early.

Which Nuxt version are you running?

Tell us the version and where it is hosted, and we will tell you what the move involves and which part carries the most risk.

Start a Nuxt conversationSee Vue development

We reply within one business day (IST).