The project is stranded on Nuxt 2
A production Nuxt 2 app with Vue 2 that is now out of support, picking up security advisories nobody is patching, and modules that will not update further on the old major.
Running on Nuxt 3+ with support
Running Nuxt?
Nuxt made SSR for Vue approachable, and then Nuxt 3 rebuilt the whole thing on Nitro and Vue 3, which left a lot of Nuxt 2 codebases stranded on an end-of-life runtime. We finish those migrations, we clean up hydration mismatches that only show up under production traffic, and we get Nitro server routes behaving on whichever host you landed on.
What it is
Nuxt is the full-stack framework for Vue, started in 2016 by Alexandre and Sebastien Chopin. It wraps Vue with file-based routing, server-side rendering, static generation, auto-imports, a modules ecosystem and sensible defaults. If Vue is the engine, Nuxt is the car around it.
Nuxt 3, released stable in 2022, rebuilt the framework on Vue 3, Vite and Nitro, its own portable server engine. Nitro compiles to many targets: Node, Vercel, Netlify, Cloudflare, Deno Deploy, AWS Lambda, Azure and plain static output. Nuxt 2, which ran on Vue 2 and Webpack, reached end of life on December 31, 2024, which means a lot of production sites are now running on an unsupported stack and need migrating.
The honest version
No technology is all upside. This is where Nuxt earns its place and where it tends to cause trouble.
Sound familiar?
The Nuxt problems that bring people to us, and what you have once each one is fixed.
A production Nuxt 2 app with Vue 2 that is now out of support, picking up security advisories nobody is patching, and modules that will not update further on the old major.
Running on Nuxt 3+ with support
Dates rendered in a different timezone server-side, data fetched only on client, or a `v-if` on a condition that is true on the server and false in the browser.
Markup stable across both renders
A node module included for a single server route, images shipped into the bundle, or a preset that is inlining dependencies it should have externalized.
Bundle fits the host's limits
`useFetch` on both server and client without a shared key, `$fetch` in a `setup` without SSR awareness, or a watcher refetching on reactive changes that should not have triggered.
One fetch per render, as intended
A `useRuntimeConfig` or `useState` call inside a plain utility that runs outside a component's setup, or inside an async boundary that lost its context.
Composables only where they belong
A store written to at module scope on the server, or a singleton-like pattern that is fine in dev and leaks between concurrent requests under real traffic.
Per-request state, no cross-contamination
H3 handlers blocking on external APIs, missing timeout and retry handling, or edge runtimes hitting Node APIs that are simulated rather than native.
Server routes fast and bounded
What we do
Hand us one failing route, or the whole Nuxt codebase.
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, at a predictable pace. Nuxt 2 and Vue 2 both reached end of life at the end of 2024, which means security fixes stop flowing, modules you depend on gradually drop support, and the hiring pool for Vue 2 is thinning. The migration to Nuxt 3 is not an afternoon, but it is a routine project with known milestones and we would rather plan it with you than rescue it in a panic later.
Almost always because server-rendered HTML and client-rendered HTML disagree on something non-deterministic: a date formatted with the server's locale, a random ID, data fetched client-side that was not present server-side, or a feature flag read from a cookie on one side only. We reproduce it against production data, make the output deterministic, and move the warnings back to zero.
Yes, that is a frequent engagement. We inventory modules, Nuxt and Vue versions, pin or upgrade them, bring hosting and environment variables under your accounts, and leave you with a repo and runbook any engineer can continue from.
If your team writes Vue, or you already own a Vue codebase, Nuxt is the natural choice and the Nuxt 3 story is mature. If you are starting fresh and your team knows React better, Next.js has a larger ecosystem and hiring pool. We will tell you which one fits based on your team, not based on which is trendier this quarter.
Marketing and content sites go well on Vercel or Netlify with ISR or prerender. Apps with long server work or non-standard Node needs go well on Node hosting. Cloudflare Workers is excellent for globally distributed reads but trips on Node APIs some modules assume. We match the preset to how the app actually behaves.
The quote is free. Send a short note about the Nuxt version and the symptom, and we respond with a price before anyone touches your code.
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: