Vue/Nuxt best practices: engineering conventions for production
Field-tested Vue/Nuxt practices from production, avoiding the common anti-patterns.
On this page
Quick answer
Which preset do I use to static-render Nuxt?
Use nitro preset:static or nuxt generate. SSR / CSR behavior differs across Nuxt majors — validate hydration before upgrading.
Machine-readable page data: /data/vue-best-practices.json
In-depth analysis
Nuxt is Vue's meta-framework, hybrid by default with first-class static generation. nuxt generate or nitro preset:static produces pure static HTML, ideal for edge distribution. Production engineering conventions revolve around "single source of truth + explicit boundaries", steering clear of the common anti-patterns.
// nuxt.config.ts — full-site static generation
export default defineNuxtConfig({
ssr: true,
nitro: { preset: 'static' },
});
// Build: nuxi generateVue/Nuxt Best Practices · Key takeaways
- Config centralized in a single source
- CI uses --frozen-lockfile
- Secrets are placeholders, never real values in code
- Docs and code live in separate places
FAQ & pitfalls
How do I cache Nuxt static pages at the edge?
generate output is atomically replaced; hash-named assets get long cache. Dynamic data is fetched on the client and does not depend on server cache.
Explore the hub
See all 5 guides in Vue & NuxtSame category as this article, sorted across the codebase.
Vue/Nuxt architecture: layered patterns for high-concurrency edge apps
The edge-delivery view of Vue/Nuxt's layering and data flow.
Vue/Nuxt deployment guide: zero-ops edge publishing with Cloudflare Pages
Git-driven Vue/Nuxt deployment in practice: commit to build, atomic publish to every edge node.
Vue/Nuxt performance tuning: push first paint and edge response to the limit
Around Vue/Nuxt's real bottlenecks, an actionable LCP / INP / CLS checklist.
Nuxt in practice: SEO-friendly static generation
Use Nuxt nitro preset:static to pre-render an entire Vue application as pure static HTML, ideal for edge distribution.
Share & save
What readers are asking
Questions that keep coming back in reader feedback, already answered.
- 01
Why is my Astro component's interactivity not working?
Components ship as zero-JS HTML by default, so an interactive one needs a client:* directive (client:load, client:visible, …). Without it the script is never bundled into the page.
See the full guide → - 02
Why is my custom Tailwind v4 brand colour not applied?
Colours must be declared in @theme (for example --color-brand). A missing @tailwindcss/vite plugin, or a leftover v3 config, makes bg-brand silently render nothing.
See the full guide → - 03
Why are _headers / _redirects not taking effect?
Both files must sit at the root of the output directory (dist/); anything under src/ is never uploaded. A purely static project should not add _worker.js either — that gives up the zero-cold-start advantage.
See the full guide →