Bye-Bye `JSON.stringify()` and `{...obj}`, Hello `structuredClone()`!
Dharmendra Kumar

Dharmendra Kumar @dharamgfx

About: ⚡I’m a curious coder who loves building things! Whether it’s creating beautiful website designs or making sure the behind-the-scenes stuff runs smoothly, I’m all in. Let’s turn code into magic! ⚡

Location:
Bihar- Bettiah
Joined:
May 19, 2024

Bye-Bye `JSON.stringify()` and `{...obj}`, Hello `structuredClone()`!

Publish Date: Sep 4 '24
117 19
  • What is structuredClone()?

    • structuredClone() is a global function introduced in 2022 that enables deep cloning of JavaScript objects. Unlike traditional methods like JSON.stringify() and JSON.parse(), which struggle with complex structures and circular references, structuredClone() handles these challenges effortlessly.
  • Why is it a game-changer?

    • It’s a robust tool for creating true deep clones, preserving the integrity of nested objects and circular references without the need for extra logic or workarounds. Plus, it's available in modern environments, including Web Workers.

1. Simple Object Cloning: The Basics

  • Using {...obj} (Shallow Copy)
  const original = { name: "Alice", details: { age: 25 } };
  const shallowCopy = { ...original };

  shallowCopy.details.age = 30;

  console.log(original.details.age); // 30
  console.log(shallowCopy.details.age); // 30
Enter fullscreen mode Exit fullscreen mode
  • What's happening?

    • The spread operator {...obj} only creates a shallow copy. The details object is not deeply cloned, so changes to shallowCopy.details affect the original details as well.
    • Using JSON.stringify() + JSON.parse() (Deep Copy)
  const original = { name: "Alice", details: { age: 25 } };
  const deepCopy = JSON.parse(JSON.stringify(original));

  deepCopy.details.age = 30;

  console.log(original.details.age); // 25
  console.log(deepCopy.details.age); // 30
Enter fullscreen mode Exit fullscreen mode
  • What's happening?

    • This method creates a deep copy, but it has limitations: it cannot handle functions, undefined, or circular references.
    • Using structuredClone() (Deep Copy)
  const original = { name: "Alice", details: { age: 25 } };
  const clone = structuredClone(original);

  clone.details.age = 30;

  console.log(original.details.age); // 25
  console.log(clone.details.age); // 30
Enter fullscreen mode Exit fullscreen mode
  • What's happening?
    • structuredClone() creates a deep clone, preserving the structure without any of the limitations of JSON.stringify() and handling complex data types like circular references and undefined.

2. Handling Circular References: A Challenge

  • Circular Reference with {...obj}
  const original = { name: "Alice" };
  original.self = original;

  // This will cause an error:
  const shallowCopy = { ...original }; // TypeError: Converting circular structure to JSON
Enter fullscreen mode Exit fullscreen mode
  • What's happening?

    • {...obj} can’t handle circular references, resulting in an error.
    • Circular Reference with JSON.stringify()
  const original = { name: "Alice" };
  original.self = original;

  // This will cause an error:
  const jsonCopy = JSON.parse(JSON.stringify(original)); // TypeError: Converting circular structure to JSON
Enter fullscreen mode Exit fullscreen mode
  • What's happening?

    • JSON.stringify() also fails with circular references, throwing an error.
    • Circular Reference with structuredClone()
  const original = { name: "Alice" };
  original.self = original;

  const clone = structuredClone(original);

  console.log(clone !== original); // true
  console.log(clone.self === clone); // true
Enter fullscreen mode Exit fullscreen mode
  • What's happening?
    • structuredClone() seamlessly handles circular references, creating a proper deep clone without errors.

3. Cloning with Functions and undefined: Another Test

  • Using {...obj}
  const original = { name: "Alice", greet: () => "Hello!", value: undefined };
  const shallowCopy = { ...original };

  console.log(shallowCopy.greet()); // "Hello!"
  console.log(shallowCopy.value); // undefined
Enter fullscreen mode Exit fullscreen mode
  • What's happening?

    • {...obj} copies functions and undefined as expected, but only shallowly.
    • Using JSON.stringify()
  const original = { name: "Alice", greet: () => "Hello!", value: undefined };
  const jsonCopy = JSON.parse(JSON.stringify(original));

  console.log(jsonCopy.greet); // undefined
  console.log(jsonCopy.value); // undefined
Enter fullscreen mode Exit fullscreen mode
  • What's happening?

    • JSON.stringify() cannot serialize functions or undefined, resulting in their loss in the cloned object.
    • Using structuredClone()
  const original = { name: "Alice", greet: () => "Hello!", value: undefined };
  const clone = structuredClone(original);

  console.log(clone.greet); // undefined
  console.log(clone.value); // undefined
Enter fullscreen mode Exit fullscreen mode
  • What's happening?
    • structuredClone() also does not clone functions but preserves undefined values, making it more reliable than JSON.stringify() for complex objects.

4. Speed and Efficiency: A Performance Note

  • Efficiency with Large Data
  const largeArray = new Array(1e6).fill({ key: "value" });

  console.time("structuredClone");
  const clone = structuredClone(largeArray);
  console.timeEnd("structuredClone");

  console.time("JSON.stringify + JSON.parse");
  const jsonCopy = JSON.parse(JSON.stringify(largeArray));
  console.timeEnd("JSON.stringify + JSON.parse");
Enter fullscreen mode Exit fullscreen mode
  • What's happening?
    • structuredClone() is often faster than JSON.stringify() + JSON.parse() for large, complex data, and avoids the pitfalls of serializing and deserializing.

5. Conclusion: Why structuredClone() is the Future

  • Reliability: Handles circular references, functions, and undefined values more predictably.
  • Efficiency: Performs deep cloning faster for large datasets and doesn’t require workarounds.
  • Simplicity: One method to rule them all—no more choosing between {...obj}, JSON.stringify(), or custom deep clone functions.

Comments 19 total

  • 85 Lokesh Dubey
    85 Lokesh DubeySep 5, 2024

    Thanks for the article.

  • Varun-Tatva
    Varun-TatvaSep 5, 2024

    Very informative.
    If we want a shallow copy of a object with having function then {...object} is the way but is there any way to deeply clone a object with having functions?.

  • Syed Muhammad Ali Raza
    Syed Muhammad Ali RazaSep 5, 2024

    👍

  • Mark Bosco
    Mark BoscoSep 5, 2024

    tks for the post

  • arvindsuriyaa
    arvindsuriyaaSep 5, 2024

    Good read !

  • jthomp
    jthompSep 5, 2024

    Neat! Thanks for the writeup!

  • Alex Petrik
    Alex PetrikSep 5, 2024

    Finally something new, that hasn't been already mentioned all over the internets . Thanks! :)

  • Gyuhang Shim
    Gyuhang ShimSep 5, 2024

    Good article. Thanks, I got a new good knowledge. :)

  • Marco Silvestroni
    Marco SilvestroniSep 6, 2024

    Good to know!

  • msegmx
    msegmxSep 6, 2024

    AI much? You didn't even care to run and print the results of 4) 🙄

  • Zach Koch
    Zach KochSep 6, 2024

    Console output is missing from section 4

  • Anurag Dubey
    Anurag DubeySep 7, 2024

    Impressive.

  • Cauê Santos
    Cauê SantosSep 8, 2024

    Thanks for the article

  • mohamed karim
    mohamed karimSep 9, 2024

    Thank for sharing

  • hufei
    hufeiSep 10, 2024

    Circular Reference with {...obj}

    Image description

  • Bernardo Gomes
    Bernardo GomesSep 10, 2024

    Thanks for sharing

  • szeredaiakos
    szeredaiakosJan 21, 2025

    Your performance assesment is a bit inaccurate. From my findings, large structures are handled faster with structuredClone but complex structures go faster with stringify.

    For large and complex it depends if it's larger than complex or complex-er than large. I don't know where exactly the threshold lies between those nor am I sure there is only one threshold.

    the "Efficiency" point of your conclusion is up for debate IMHO. The other points are clearly not debatable.

Add comment