Which stats preset balances CI/CD log verbosity with error trace completeness for deployment failure diagnosis?

Goal

Configure webpack build output so that CI/CD pipelines capture enough error context to diagnose deployment failures while keeping log volume manageable.

Constraints

• Stats presets (errors-only, minimal, verbose, detailed) differ in verbosity and default between CLI and programmatic API.
• errorDetails: true adds stack, module, and chunk traces but may expose internal file paths in production logs.
• JSON stats (--json or stats: 'json') enable programmatic parsing, yet the schema can shift between webpack 5 minor releases.
• Persistent filesystem cache can serve stale artifacts unless the cache directory is excluded from deployment artifacts.

Questions

1. Which stats preset delivers sufficient error context without flooding CI logs?
2. Does enabling errorDetails leak sensitive paths in a production environment?
3. Can the JSON stats schema be considered stable across webpack 5.x patches for automated log analysis?