structuredClone ships in Node 17+ and every evergreen browser. Unlike a JSON round-trip, it preserves Date, RegExp, Map, Set, ArrayBuffer, typed arrays, and even circular references via the HTML structured-clone algorithm. The clone is fully detached, so mutating the copy never leaks back into the source. The only common types it cannot copy are functions, DOM nodes, and class instances with non-cloneable internal slots (it throws DataCloneError for those). Use this version by default for plain data.

The JSON round-trip is fast and dependency-free, but it silently downgrades types: Date becomes an ISO string, Map/Set become {}, typed arrays become plain numeric-keyed objects, undefined and functions disappear, and BigInt throws. It also cannot represent cycles. It still has a niche for tiny configuration objects in legacy environments, or when you explicitly want a JSON-safe snapshot. Reach for structuredClone first; only drop to this when you must support a runtime older than Node 17.

Sometimes you need cloning behaviour that structuredClone cannot give you: skipping certain keys, copying class instances with custom prototypes, or running in a sandbox without the global. The recursive version handles cycles by memoising every node in a WeakMap keyed by the source reference. Reflect.ownKeys covers both string and symbol keys, and preserving Object.getPrototypeOf keeps class instances usable. The trade-off is that you now own the type table (Date, RegExp, and any custom types you care about); each new type adds another branch.