Waleed 0ae09c1518 fix(logger): never let structured serialization throw into the caller (#6331) ...

* fix(logger): never let structured serialization throw into the caller

In production the JSON branch merged caller-supplied arguments into the log
entry and stringified it with no error handling. A cyclic reference, a BigInt,
or a throwing getter in that metadata raised a TypeError out of `logger.info`
and friends: the line was lost and the caller's code path aborted.

Dev was unaffected — the colorized branch already routes objects through
`formatObject`, which catches — so this class of bug is invisible locally and
only surfaces in production, where it reads as structured logs disappearing
while raw stack traces keep shipping.

Build and serialize through `serializeEntry`, which falls back to a
cycle/BigInt-tolerant replacer and then to a minimal entry flagged with
`serializationError`.

* fix(logger): keep hostile child metadata from throwing into the caller

* fix(logger): keep a throwing toJSON from escaping the final fallback

* fix(logger): keep repeated references out of the circular-reference fallback

2026-08-06 13:33:41 -07:00

..

src

fix(logger): never let structured serialization throw into the caller (#6331)

2026-08-06 13:33:41 -07:00

package.json

chore(typescript): upgrade to TypeScript 7 (native Go compiler) (#5521)

2026-07-08 16:41:23 -07:00

tsconfig.json

improvement(monorepo): added tsconfig package, resolved type errors in testing package (#2613)

2025-12-28 00:36:48 -08:00

vitest.config.ts

fix(build): update dockerfile to contain testing package deps (#2591)

2025-12-26 12:20:38 -08:00