immutable-js VS valtio

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

We took inspiration from the many frameworks we worked with throughout our careers. And maybe surprisingly, Django’s ORM layer impacted our design choices and the API quite a bit. The resulting framework relies on Zod for schemas and validation and Valtio for React integration.

Valtio is like simplified MobX

Even simpler than Zustand are state-atom libraries like jotai or recoil, or proxy based ones like valtio. Here's some discussion about the differences.

There is a package developed around this proxy concept called Valtio which is available for JavaScript, React, and so on... feel free to check and star it on Github.

I'm switching from redux-saga to valtio (https://github.com/pmndrs/valtio) for now. It's simple and easy to use, everything's great so far.

I like valtio, works w/ React or just js. Has subscribe, derive, and more.

https://github.com/pmndrs/valtio

Jotai and Valtio are both also really good. Recently looked at Nanostore as well and has some similarity to Jotai and Recoil.

Since we want the React component to react to an external change, using a state manager makes this easy. We will use Valtio here by example. For this library, change the esbuild config to --target=es2020 instead to remove some warnings (for example, the Zustand library is ok).