Snapshots are the immutable serialization, in plain objects, of a tree at a specific point in time . Snapshots can be inspected through getSnapshot(node, applyPostProcess) . Snapshots don’t contain any type information and are stripped from all actions, etc., so they are perfectly suitable for transportation.
Read moreAre MobX actions asynchronous?
Asynchronous actions In essence, asynchronous processes don’t need any special treatment in MobX, as all reactions will update automatically regardless of the moment in time they are caused.
Read moreWhat is computed in MobX?
Computed values are automatically derived from your state if any value that affects them changes . Computed values can be optimized away in many cases by MobX as they are assumed to be pure. For example, a computed property won’t re-run if none of the data used in the previous computation changed.
Read moreWhat is a MobX action?
An action is any piece of code that modifies the state . In principle, actions always happen in response to an event. For example, a button was clicked, some input changed, a websocket message arrived, etc. MobX requires that you declare your actions, although makeAutoObservable can automate much of this job.
Read moreWho created MobX?
One of the most interesting quotes I’ve found from Michel Weststrate (the founder of MobX): Reacting to state changes is always better then acting on state changes.
Read moreHow big is MobX?
The gzipped minified build size dropped from 17.3kB to 14.2kB (22% smaller). But, in practice this will shave off even a bit more, as MobX 4 is better tree-shake-able.
Read moreWhat is MobX state?
mobx-state-tree (also known as “MST”) is a state container that combines the simplicity and ease of mutable data with the traceability of immutable data and the reactiveness and performance of observable data .
Read more