fix(nuxt): log errors thrown when booting the nuxt app

[danielroe]

🔗 Linked issue

resolves #19162

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

This ensures we don't swallow plugin errors, in development mode at least. We could also consider adding a warning if user doesn't register their own handler?

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[pi0]

Nice find. Since we don't suppress other errors from console by default why not also doing for production?

[danielroe]

We do suppress errors in other places (in that we require users to handle them), specifically when it comes to universal router errors and in useAsyncData/useFetch. But in this case I am very persuadable.

[devilmark84]

Hello, I've just installed the new 3.2.3 version of Nuxt and now this happens when a page is not found.

[nuxt] error caught during app initialization H3Error: Page not found: /robots.txt                                                                                          11:13:52
    at Module.createError (file:///Users/marco/Desktop/nuxt-bootstrap/node_modules/h3/dist/index.mjs:128:15)
    at /Users/marco/Desktop/nuxt-bootstrap/node_modules/nuxt/dist/pages/runtime/plugins/router.mjs:141:113
    at triggerAfterEach (file:///Users/marco/Desktop/nuxt-bootstrap/node_modules/vue-router/dist/vue-router.mjs:3306:13)
    at file:///Users/marco/Desktop/nuxt-bootstrap/node_modules/vue-router/dist/vue-router.mjs:3209:13
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /Users/marco/Desktop/nuxt-bootstrap/node_modules/nuxt/dist/pages/runtime/plugins/router.mjs:157:7
    at async createNuxtAppServer (/Users/marco/Desktop/nuxt-bootstrap/node_modules/nuxt/dist/app/entry.mjs:30:7)
    at async default (file:///Users/marco/Desktop/nuxt-bootstrap/node_modules/@nuxt/vite-builder/dist/runtime/vite-node.mjs:27:18)
    at async Object.renderToString (file:///Users/marco/Desktop/nuxt-bootstrap/node_modules/vue-bundle-renderer/dist/runtime.mjs:172:19)
    at async file:///Users/marco/Desktop/nuxt-bootstrap/.nuxt/dev/index.mjs:791:21 {
  statusCode: 404,
  fatal: false,
  unhandled: false,
  statusMessage: 'Page not found: /robots.txt',
  __nuxt_error: true
}

Is this behavior what you wanted? 🧐 How can I suppress these errors or catch them?

Thank you

[pi0]

I also spotted same issue. I guess we might apply a filter to hide internal type of errors (i guess we added a field for it /cc @danielroe )