Nuxt•4w ago

500 on preview, fine in dev

My Nuxt3 app works perfectly in dev mode - when I build (deploy or npm run preview (after build)) it just seems to only ever give me a 500. No errors in any consoles, I'm little confused on what to even do next in order to debug it further? Can I run a "built" version in debug so it at least points me to errors?

3 Replies

kapa.ai•4w ago

Hi @Bread. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- To debug your Nuxt 3 application that's working fine in development mode but giving a 500 error in preview or production, you can try the following approaches: 1. Enable sourcemaps: Sourcemaps can help you debug your built application. You can enable them in your Nuxt configuration file as described in the documentation (https://nuxt.com/docs/guide/going-further/debugging#sourcemaps):

export default defineNuxtConfig({
  sourcemap: {
    server: true,
    client: true
  }
})

export default defineNuxtConfig({
  sourcemap: {
    server: true,
    client: true
  }
})

2. Use Node Inspector: You can use Node Inspector to debug your Nuxt server-side code. Run the following command as mentioned in the docs (https://nuxt.com/docs/guide/going-further/debugging#debugging-with-node-inspector):

nuxi dev --inspect

nuxi dev --inspect

3. Debug in your IDE: You can set up debugging configurations in your IDE to debug both the server and client sides of your Nuxt application. The documentation provides examples for VS Code (https://nuxt.com/docs/guide/going-further/debugging#debugging-in-your-ide) and JetBrains IDEs (https://nuxt.com/docs/guide/going-further/debugging#example-jetbrains-ides-debug-configuration). 4. Check for errors during the build process: Make sure there are no errors during the build process. Sometimes, errors that don't show up in development can occur during the build. 5. Verify your start command: Ensure you're using the correct command to start your production server. It should be node .output/server/index.mjs as shown in this example (https://stackoverflow.com/questions/77345823). 6. Check your dependencies: Make sure all required dependencies are properly installed and listed in your package.json file. Sometimes, moving dependencies from devDependencies to dependencies can resolve issues in production. 7. Review your error handling: Make sure you have proper error handling in place. You can use the vue:error hook or set up a global error handler (https://nuxt.com/docs/getting-started/error-handling#vue-errors) to catch and log errors that might be occurring. If you're still unable to identify the issue, you might want to report a bug to the Nuxt team (https://nuxt.com/docs/community/reporting-bugs). Make sure to provide as much detail as possible about your setup and the steps to reproduce the issue. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•4w ago

<@280730525960896513> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

BreadOP•4w ago

The above isn't really useful, because it works fine when debugging in dev mode.

Gaming

Programming

500 on preview, fine in dev