You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-1Lines changed: 6 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -21,10 +21,15 @@
21
21
<br/>
22
22
</div>
23
23
24
+
7kb MobX-level memoization library, which tracks all the arguments you are __really__ depends on.
25
+
- It is not so fast, as reselect, but could handle more cases, and works out of the box.
26
+
- It is not so fast, but much faster, than _VDOM tree comparison_ you will face in case of render trashing.
27
+
- It contain 3 types of memoziation to handle all possible cases.
24
28
25
-
7kb library to change the world. It is not fast, but it is MUCH react-memoizer that VDOM tree comparison you will face in case of render trashing.
26
29
Uses [memoize-state](https://github.com/theKashey/memoize-state) underneath, providing the same magic for `get` as [immer](https://github.com/mweststrate/immer) provided to `set`.
27
30
31
+
Works fine in all browsers including IE11.
32
+
28
33
__Just write code as you want. It it will be properly memoized__.
29
34
30
35
This is declarative component memoization for React! Based on [Dan Abramov's tweet](https://twitter.com/dan_abramov/status/965378278461755392)
0 commit comments