---
title: "Discussion on \"structuredClone vs JSON.parse(JSON.stringify()) for Deep Copying in Node.js\" | Hashnode"
description: "Discussion on \"structuredClone vs JSON.parse(JSON.stringify()) for Deep Copying in Node.js\". I copied a config object the way everyone does it. JSON.parse(JSON.stringify(obj)), one line, done. The object had a Date in it and a Map. The copy came back, the code ran, and half an hour later some"
url: "https://hashnode.com/posts/structuredclone-vs-json-parse-json-stringify-for-deep-copying-in-node-js/6af55d3803f632951bc1deb9"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [structuredClone vs JSON.parse(JSON.stringify()) for Deep Copying in Node.js](https://aheadkit.hashnode.dev/structuredclone-vs-json-parse-json-stringify-for-deep-copying-in-node-js?utm_source=hashnode&utm_medium=feed)

I copied a config object the way everyone does it. JSON.parse(JSON.stringify(obj)), one line, done. The object had a Date in it and a Map. The copy came back, the code ran, and half an hour later some

1d ago · 5 min read · aheadkit.hashnode.dev  
Read the article

-   [#javascript](https://hashnode.com/tag/javascript)
-   [#node](https://hashnode.com/tag/node)
-   [#programming](https://hashnode.com/tag/programming)
-   [#webdev](https://hashnode.com/tag/webdev)

## Written by

[Abdus Salam](https://hashnode.com/@aheadkit)

@aheadkit

  
[View profile](https://hashnode.com/@aheadkit)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.