Guide · Framework
Deploy Nuxt generate to Novence
npx nuxt generate writes .output/public. Pass that path — the CLI does not auto-detect it.
Nuxt can prerender every route into HTML via nuxt generate. That static tree lives in .output/public, which is not one of the CLI’s auto-detect names (dist, build, out, public, _site). Always pass the path.
Configure
Use npx nuxt generate (or nitro.preset: "static"). Keep ssr: true during generate so pages are prerendered to HTML. ssr: false is SPA mode: one index.html and client routes that 404 on refresh because Novence has no fallback rewrite.
Do not deploy .output/server. There is no Node or Nitro runtime on Novence. Server routes, useAsyncData that only run on the server, and hybrid rendering will not execute after upload.
// nuxt.config.ts
export default defineNuxtConfig({
ssr: true,
nitro: {
preset: "static",
},
router: {
options: {
strict: false,
},
},
});Build
npx nuxt generate
npx nuxt generate crawls your routes and writes HTML under .output/public. Confirm .output/public/index.html before deploying.
Deploy
npx novence deploy .output/public
npx novence deploy .output/public — required. Omitting the path will miss this folder. Payload and _nuxt/ assets in that directory upload as static files.
.output/public is not in the CLI auto-detect list. Pass it every time. Full CLI: /cli.
Caveats
- The CLI will not find
.output/publicon its own. - SPA-only Nuxt (
ssr: false) is a poor fit unless every URL is also prerendered. - API routes in
server/are not hosted. Call public APIs from the client or bake data into the generate step.
FAQ
Why not nuxt build?
nuxt build is for a Node/Nitro server. nuxt generate prerenders HTML. Only the generate output belongs on Novence.
Where is the output?
.output/public. Pass it explicitly: npx novence deploy .output/public.
Can I use Nuxt server routes?
Not on Novence. Prerender data at generate time, or fetch a public API from the browser.
Agents ship. Novence hosts.
Copy Prompt or get a key. Then npx novence deploy .output/public.