feat: better errors

[pi0]

This PR improves request error handlers with different implementations for development and production.

Followup:

• Upstream sourcemap loader support to youch-core as an opt-in feature
• Track ansi wrap issue

Errors in development

Using poppinss/youch 4.x for HTML rendering: (only if accept header explicitly includes text/html ~ browsers)

Note

Sourcemaps for the app are automatically applied, without the need of NODE_OPTIONS="--enable-source-maps".

JSON responses (when the accept header does not include text/html) are consistent with production errors and have more useful fields:

{
  "error": true,
  "url": "http://localhost:3000/",
  "statusCode": 500,
  "statusMessage": "Server Error",
  "message": "This is an error",
  "data": {
    "foo": "bar"
  },
  "stack": [
    "This is an error",
    "at createError (/Users/pooya/Code/nitro/node_modules/.pnpm/[email protected]/node_modules/h3/dist/index.mjs:72:15)",
    "at Object.handler (/Users/pooya/Code/nitro/playground/routes/index.ts:2:0)",
    "at Object.handler (/Users/pooya/Code/nitro/node_modules/.pnpm/[email protected]/node_modules/h3/dist/index.mjs:1889:24)",
    "at Object.handler (/Users/pooya/Code/nitro/node_modules/.pnpm/[email protected]/node_modules/h3/dist/index.mjs:2202:34)",
    "at Object.handler (/Users/pooya/Code/nitro/node_modules/.pnpm/[email protected]/node_modules/h3/dist/index.mjs:1963:31)",
    "at process.processTicksAndRejections (node:internal/process/task_queues:105:5)",
    "at async Server.toNodeHandle (/Users/pooya/Code/nitro/node_modules/.pnpm/[email protected]/node_modules/h3/dist/index.mjs:2255:7)"
  ]
}

For console errors (for unhandled or fatal errors) use consola + Youch.toANSI and include more info including method, URL, cause and source 🔥

Worker entry errors are now also improved by leveraging the same dev error handler:

Errors in production

Nitro errors in production are always JSON with application/json mime:

{
  "error": true,
  "url": "http://localhost:3000/",
  "statusCode": 500,
  "statusMessage": "Server Error",
  "message": "Server Error",
  "data": {
    "foo": "bar"
  }
}

Server console errors include request info, and error data + cause (if any) using native runtime console.error handler for formatting:

Note

In production, NODE_OPTIONS="--enable-source-maps" is required in order to enable sourcemaps.