fix(to-response): only mark true cycles in safeStringify

[bytaesu]

• Closes safeStringify should only mark true cycles as circular references, not shared objects #86

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/better-call@140

commit: cb08dd6

[Copilot]

Pull request overview

Adjusts safeStringify in toResponse to only label true cycles as circular references (matching JSON.stringify behavior for shared-but-non-cyclic references), addressing issue #86.

Changes:

• Reworked circular detection in safeStringify to check only the current ancestor chain (not “seen before” globally).
• Updated/added tests to ensure shared object/array references serialize in full while true cycles are still marked.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
packages/better-call/src/to-response.ts	Updates safeStringify to detect only ancestor-chain cycles using parent tracking + stable IDs.
packages/better-call/src/to-response.test.ts	Updates circular-ref expectations and adds coverage for shared non-cyclic references (object + array).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[better-release]

Successfully created backport PR for v1.3.x:

• [backport v1.3.x] fix(to-response): only mark true cycles in safeStringify #141