limu VS superjson

limu is designed for modern browsers. It only considers the operating environment that supports Proxy and uses the mechanism of shallow copy on read and mark update on write. This allows users to operate variable data like original data. During the operation, only proxy objects are generated for the read nodes and returned to the user. After reading, the parent and child nodes are directly connected with shallow clone nodes. The proxy object is hidden in the meta data of the node. , after the operation is completed, a new data with structural sharing characteristics is generated, and the meta data generated during the reading process is removed.

for those recommending Immer, check out Mutative or Limu instead (much faster)

https://github.com/unadlib/mutative

https://github.com/tnfe/limu

Strongly recommend trying [limu](https://github.com/tnfe/limu)，it is now the fastest immutable data js lib，and it is also production environment available.

//You can verify through the following tests, and you are also welcome to add more performance test cases

Welcome to understand and pay attention to limu, visit documentation and right-click to bring up the console, you can ** Real-time experience **limu api and immer api for comparison (limu and immer objects are bound globally).

You are very welcome to submit your test to the benchmark directory of limu git repo

limu 🍋

I wasn't aware of this, I would like to give a shout out to superjson (https://github.com/blitz-js/superjson) which I had been using to solve this problem. I will look at this solution for next time.

Here you go https://github.com/blitz-js/superjson

superjson has a plugin system and also supports ObjectId. https://github.com/blitz-js/superjson/pull/71

Hey Mahmoud from Prisma here 👋🏼 Next.js doesn't serialize the Date type. There are a couple of workarounds discussed in this GitHub discussion. Personally, I found that using superjson to be the simplest approach.