[bug] API error responses expose stack traces in production

[R-udren]

bug description:
The Cap standalone server currently exposes stack traces in API error responses, which reveals internal implementation details to end users.

affects:

• js server

to reproduce:

• Deploy the Cap standalone server using the Docker image tiago2/cap:latest from the docs https://trycap.dev/guide/#_1-run-the-server
• Make a request to a non-existent endpoint (e.g., GET /test)
• Observe the error response contains a full stack trace

Example:

{
  "success": false,
  "error": "NOT_FOUND",
  "detail": {
    "name": "Error",
    "message": "NOT_FOUND",
    "stack": "Error\n    at anonymous (file:///usr/src/app/node_modules/elysia/dist/compose.mjs:12:33)\n    at composeGeneralHandler (/usr/src/app/node_modules/elysia/dist/compose.mjs:1187:3)\n    at compile (/usr/src/app/node_modules/elysia/dist/index.mjs:1878:119)\n    at \u003Canonymous\u003E (/usr/src/app/node_modules/elysia/dist/adapter/bun/index.mjs:201:29)\n    at processTicksAndRejections (unknown:7:39)",
    "code": "NOT_FOUND"
  }
}

expected behavior:
Deployment by following docs guide does not include stack trace in details.

[tiagozip]

hi, you can follow our docs for details on how to obfuscate stack traces.

[R-udren]

Hi! Thanks for quick response and beautiful project :)

My take is that it should be hidden by default in deploy code example from the docs.

DISABLE_ERROR_LOGGING: true
SHOW_ERRORS: false

Didn't helped too.