nuxtjs
Nuxt.js Errors
Errors emitted by Nuxt.js, the Vue meta-framework. Covers build-time, prerendering, and runtime errors produced by Nuxt 3 and its underlying Nitro server engine.
10 codes
references nuxt.com/docs/guide/concepts/error-handlingnuxt.com/docs/api/composables/use-errorgithub.com/nuxt/nuxt
· All codes 10 codes
- NUXT_APP_MANIFEST_ERROR App Manifest Error Nuxt failed to fetch or parse the app manifest at /_nuxt/builds/meta/<buildId>.json. The manifest is used for granular cache invalidation and island routing. This can happen after a deployment if CDN or browser caches serve a stale manifest. A hard reload usually resolves it.
- NUXT_CHUNK_LOAD_FAILED Chunk Load Failed A lazily loaded JavaScript chunk (e.g. a dynamically imported component or page) could not be fetched at runtime. This is usually caused by a new deployment invalidating old chunk hashes while users still have the previous version open. A full page reload typically resolves it.
- NUXT_ERROR_UNHANDLED Unhandled Error An error was thrown inside a Nuxt lifecycle hook or middleware that was not caught by a try/catch or error boundary. Nuxt captures it and routes it to the global error page (error.vue). Add an error.vue to the project root to customise how this is displayed to users.
- NUXT_HYDRATION_ERROR Hydration Error The HTML rendered on the server does not match what Vue produced on the client during hydration. Common causes include accessing browser-only globals (window, document) outside of onMounted, using Date.now() or Math.random() without a seed, or conditional rendering based on cookies that differ between server and client.
- NUXT_ISLAND_ERROR Island Error A Nuxt Server Component (island) failed to render. Islands render in isolation on the server; if the island throws, Nuxt replaces it with an error slot or the global error page. Inspect the server logs for the underlying exception inside the island component.
- NUXT_MODULE_SETUP_FAILED Module Setup Failed A Nuxt module listed in nuxt.config.ts threw an error during its setup hook. Check that the module is compatible with your Nuxt version, all required options are provided, and any peer dependencies are installed.
- NUXT_PAYLOAD_EXTRACTION_FAILED Payload Extraction Failed Nuxt could not extract the payload for a page during static generation (nuxi generate). This typically means the page threw an error or the server-side data fetching (useAsyncData / useFetch) failed. Check the route's server logs for the underlying error.
- NUXT_PLUGIN_ERROR Plugin Error A Nuxt plugin (a file in the plugins/ directory) threw an error during app initialisation. Plugins run before the root Vue component is mounted, so an unhandled error here prevents the entire app from starting. Wrap plugin code in a try/catch and use useError() to surface errors gracefully.
- NUXT_PRERENDER_NO_ROUTES_DETECTED Prerender: No Routes Detected The Nuxt crawler found no routes to prerender. This happens when the app has no statically discoverable links from the root page, or when crawlLinks is false and no explicit routes are listed under nitro.prerender.routes. Add routes explicitly or enable link crawling.
- NUXT_PRERENDER_ROUTE_FAILED Prerender: Route Failed A specific route threw an error or returned a non-2xx status code during static prerendering. By default Nuxt fails the build on any prerender error. Set nitro.prerender.failOnError to false to treat prerender errors as warnings and continue generating other routes.