Do Pug compilation errors propagate to deployment logs or get suppressed?

Goal

Determine whether Pug template compilation failures reach the deployment pipeline or are suppressed by application error handling when rendering fails in production.

Constraints and uncertainty

Pug throws a compilation error for invalid template syntax, but a server or framework may catch that exception during rendering and emit only a generic message. Log-level filtering can hide warnings, and error-reporting behavior may vary across Pug major versions. It is unclear whether the original stack trace belongs in the deployment log or in a separate application error entry.

Does Pug propagate compilation errors to the deployment pipeline by default? Should compilation errors be logged separately from rendering errors? What log level captures Pug template syntax failures in production?