@bymax-one/nest-logger 1.3.0 → 1.3.1

package/CHANGELOG.md

@@ -11,6 +11,34 @@ heading here.
 
 ## [Unreleased]
 
+## [1.3.1] - 2026-08-18
+
+### Documentation
+
+- **`excludePaths` says what its defaults do not reach.** The defaults are
+  `[/^\/health$/, /^\/metrics$/]`, and `@bymax-one/nest-core` serves liveness and readiness at
+  `/health/live` and `/health/ready` with no bare `/health` at all — so the default excludes a
+  route that does not exist while logging both probes. A consumer running both measured **8272 of
+  8274** HTTP entries as the liveness probe, at one container healthcheck every ten seconds; at
+  orchestrator volume it is the same shape with more zeros. There is no error and no warning, and
+  the config reads as though it were handled.
+
+  The defaults are **not** widened, and the reason is checkable rather than a preference: both
+  prefixes are configurable there (`DEFAULT_HEALTH_PATH`, `DEFAULT_METRICS_PATH`). A default
+  naming specific subpaths would be less wrong rather than correct, and a prefix pattern would
+  silently swallow a consumer's own `/health/*` route they did want logged. Excluding a path
+  decides which requests vanish from the record, so it stays explicit — the docblock now carries
+  the one-line fix for the stock layout, and it ships in the `.d.ts` where someone wiring the two
+  libraries reads it.
+
+### Internal
+
+- **The last surviving mutant is gone, by deletion rather than annotation.** A `catch` in
+  `report-destination-failure` re-assigned `undefined` to a variable already `undefined` from its
+  declaration, so emptying the block changed no output for any input and no test could kill it. A
+  Stryker directive was tried first and was not honoured at that position. The project scores
+  **100.00** on a cold run: 1515 mutants, 841 killed, zero survivors, 145 documented equivalents.
+
 ## [1.3.0] - 2026-08-18
 
 ### Fixed
@@ -1794,7 +1822,8 @@ published `dist/` is identical — no runtime behaviour changes for consumers.
 - Professional CI suite: `ci.yml`, `bench.yml`, `codeql.yml`, `scorecard.yml`,
   `release.yml`, Dependabot, and issue templates
 
-[Unreleased]: https://github.com/bymaxone/nest-logger/compare/v1.3.0...HEAD
+[Unreleased]: https://github.com/bymaxone/nest-logger/compare/v1.3.1...HEAD
+[1.3.1]: https://github.com/bymaxone/nest-logger/compare/v1.3.0...v1.3.1
 [1.3.0]: https://github.com/bymaxone/nest-logger/compare/v1.2.9...v1.3.0
 [1.2.9]: https://github.com/bymaxone/nest-logger/compare/v1.2.7...v1.2.9
 

package/dist/server/index.cjs

@@ -1137,7 +1137,6 @@ function safeMinLevel(destination) {
     const read = destination.minLevel;
     resolved = isLogLevel(read) ? read : void 0;
   } catch {
-    resolved = void 0;
   }
   resolvedMinLevels.set(destination, resolved);
   return resolved;

package/dist/server/index.d.cts

@@ -260,6 +260,21 @@ interface HttpOptions {
      * Paths that bypass HTTP logging (health checks, metrics). Defaults:
      * `/health`, `/metrics`.
      *
+     * The defaults do NOT cover `@bymax-one/nest-core`, and that is the common case
+     * worth knowing before you rely on them. It serves liveness and readiness at
+     * `/health/live` and `/health/ready`, and no bare `/health` at all, so
+     * `/^\/health$/` excludes a route that does not exist while both probes are
+     * logged. Measured on one deployment: 8272 of 8274 HTTP entries were the
+     * liveness probe. Set `excludePaths` yourself when wiring the two together —
+     * `[/^\/health\/(live|ready)$/, /^\/metrics$/]` matches the stock layout.
+     *
+     * The defaults are not widened to include those subpaths because both prefixes
+     * are CONFIGURABLE there (`DEFAULT_HEALTH_PATH`, `DEFAULT_METRICS_PATH`): any
+     * default naming specific subpaths would be less wrong rather than correct, and
+     * a prefix pattern would silently swallow a consumer's own `/health/*` route
+     * that they did want logged. Excluding a path is a decision about which requests
+     * disappear from the record, so it stays explicit.
+     *
      * SECURITY: each pattern is `.test()`-ed against the (attacker-controllable)
      * request path on every request. Supply only anchored, linear-time regexes
      * (e.g. `/^\/health$/`); a pattern with catastrophic backtracking would turn a

package/dist/server/index.d.ts

@@ -260,6 +260,21 @@ interface HttpOptions {
      * Paths that bypass HTTP logging (health checks, metrics). Defaults:
      * `/health`, `/metrics`.
      *
+     * The defaults do NOT cover `@bymax-one/nest-core`, and that is the common case
+     * worth knowing before you rely on them. It serves liveness and readiness at
+     * `/health/live` and `/health/ready`, and no bare `/health` at all, so
+     * `/^\/health$/` excludes a route that does not exist while both probes are
+     * logged. Measured on one deployment: 8272 of 8274 HTTP entries were the
+     * liveness probe. Set `excludePaths` yourself when wiring the two together —
+     * `[/^\/health\/(live|ready)$/, /^\/metrics$/]` matches the stock layout.
+     *
+     * The defaults are not widened to include those subpaths because both prefixes
+     * are CONFIGURABLE there (`DEFAULT_HEALTH_PATH`, `DEFAULT_METRICS_PATH`): any
+     * default naming specific subpaths would be less wrong rather than correct, and
+     * a prefix pattern would silently swallow a consumer's own `/health/*` route
+     * that they did want logged. Excluding a path is a decision about which requests
+     * disappear from the record, so it stays explicit.
+     *
      * SECURITY: each pattern is `.test()`-ed against the (attacker-controllable)
      * request path on every request. Supply only anchored, linear-time regexes
      * (e.g. `/^\/health$/`); a pattern with catastrophic backtracking would turn a

package/dist/server/index.mjs

@@ -1134,7 +1134,6 @@ function safeMinLevel(destination) {
     const read = destination.minLevel;
     resolved = isLogLevel(read) ? read : void 0;
   } catch {
-    resolved = void 0;
   }
   resolvedMinLevels.set(destination, resolved);
   return resolved;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@bymax-one/nest-logger",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "description": "Structured JSON logging for NestJS based on Pino 10, with optional OpenTelemetry correlation.",
   "author": "Bymax One <support@bymax.one>",
   "license": "MIT",