immutable-js VS immutability-helper

immutable for JavaScript.

Check out Object.freeze. There's also Immutable.js for working with immutable data.

Use immutability to manage state updates When updating state in your React application, it's important to ensure that you are not mutating the original state object. Instead, you should create a new copy of the state object with the updated values. Immutability makes it easier to manage state updates and ensures that the updates are performed in a predictable and safe manner. Libraries like Immutable.js provide a set of functions that simplify working with immutable data in React applications.

We're wanting to get rid of immutable so I'm trying to replicate what it is about the Record functionality and types that allow this dynamic property access to work. After pulling my hair out looking through the [email protected] type definitions and the actual code, to me it looks like the types are just kind of lying about what's going on ... and it's just working. Does anyone have any ideas how I can replicate this dynamic property access with strong typings?

The Immutable.js README has a much more complete description of immutability and why you might want to use the library. Also worth mentioning that Immer is an alternative which is a bit easier to get started with.

Examples: immutable-js Immer

I can't speak to C# and Java, but the suggestion in this post: ImmutableJS already uses Persistent data structures. (It's the second sentence of their introduction)

Avoiding mutation is just never modifiyng an object, ever. There are tons of implementations of this pattern, notably immutable.js (https://immutable-js.com/), Redux is also an example of this philosophy.

JavaScript is most programers' first introduction to map, filter, and reduce. Easy lambdas made those higher-order functions a staple of a lot of JS code.

Meanwhile, immutable.js[0] is at 10 million downloads per week and rising.

I would add that it's not just the ease of use of lambdas, but the fact that in JavaScript functions really are first class citizens. Most of the other widely used languages that people start on have lambda functions added in as a bit of a hack and only treat some functions as real values.

[0] https://www.npmjs.com/package/immutable

if you're feeling fancy, try out https://www.npmjs.com/package/immutability-helper

Here’s a lib that could help: https://github.com/kolodny/immutability-helper

https://reactjs.org/docs/introducing-jsx.html https://www.freecodecamp.org/news/what-the-heck-is-jsx-and-why-you-should-use-it-to-build-your-react-apps-1195cbd9dbc6/ https://egghead.io/learn/react/beginners/wtf-is-jsx https://danburzo.github.io/react-recipes/recipes/immutability.html https://reactkungfu.com/2015/08/pros-and-cons-of-using-immutability-with-react-js/ https://github.com/kolodny/immutability-helper https://www.dottedsquirrel.com/declartive-imperative/

I'm OK to use any of the libraries immutability-helper, immutable-js etc or ES6. I've tried and googled this for over 4 hours, and still cannot wrap my head around it. Would be extremely grateful for some help.

I doubt that’s true, check this out, it’s designed with your use case in mind.

This tutorial uses the create-react-app as the starting template. The react and react-dom dependencies are both version 17.0.2. The react-scripts is version 4.0.0. The yup library is the fourth dependency and it is version 0.32.9. The fifth and last dependency is immutability-helper, version 3.1.1.

Are you perplexed by the syntax of immutability-helper? Repulsed by immer.js's use of assignment? Alarmed by lodash's lack of type safety?

If you still insist using a deeply nested and quite complex object, I would advise you look at immutability-helper - https://github.com/kolodny/immutability-helper or similar immutable library.