fix(clone): support circular references

[CyberneticX-Tech]

Closes #104

Problem

clone recurses unconditionally, so a value that references itself overflows the call stack:

const obj: any = {};
obj.self = obj;
clone(obj); // RangeError: Maximum call stack size exceeded

const arr: any[] = [];
arr[0] = arr;
clone(arr); // RangeError: Maximum call stack size exceeded

Fix

Track visited values in a WeakMap and register each container in it before cloning its children, so a cycle resolves to the clone already in progress. A value that appears more than once is now cloned once and shared by every reference in the output, which matches structuredClone semantics.

cloneMap previously round-tripped through Object.fromEntries/Object.entries, which coerced non-string keys to strings. It now iterates the map directly, so new Map([[{ id: 1 }, 'foo']]) keeps its object key.

The WeakMap is created per top-level clone call, so nothing is retained between calls.

Tests

Added regression coverage for self-referencing objects, arrays, maps and sets, a mutually referencing pair, shared-reference identity, and non-string map keys.

Full suite passes (616 tests), plus type-check, eslint and build.

[github-actions]

🎉 This PR is included in version 4.24.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀