limu VS monocle-ts

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 🍋

Instead of the "deep path properties" syntax, you might want to take the opportunity to learn about functional lenses with monocle-ts

https://gcanti.github.io/monocle-ts/

You may be interested also in checking out the implementation of Lens in monocle-ts, one of the libraries in the fp-ts ecosystem

For anyone - anyone who's faffed around with JavaScript's spread syntax when working with nested immutable data, anyway - struggling to understand the general concept or utility of lenses, I'd encourage looking into monocle-ts. The motivation [0] that kicks off the README instantly made me a believer, and TypeScript's idiosyncratic type system makes using the library remarkably natural; it fits right in without needing to deal with anything analogous to Template Haskell.

[0] https://github.com/gcanti/monocle-ts#motivation

You could have a look at the monocle-ts library. It was designed to deal with this kind of problem.

spectacles-ts integrates seamlessly with the fp-ts ecosystem (it's built on top of the excellent monocle-ts library)

lenses help with this quite a bit, check out monocle-ts

You notice that Getters are composable as they are just pure functions, but the fact that setters are mutating values is not that nice. Tho, at this point we have invented quasi mutable lenses and If you really want you might invent actual purely functional lenses as well, but that’s for another day. Meanwhile you can take a look at an actual typescript lesses library from @gcanti / monocle-ts.