Memoized selectors for Redux and other immutable object derivation.
Rememo's default export is a function which accepts two arguments: the selector function whose return value is to be cached, and a second function which returns the reference or array of references upon which the selector's derivation depends. The return value is a new function which accepts the same arguments as the selector.
;const getTasksByCompletion =;// The selector will only calculate the return value once so long as the state// `todo` reference remains the samelet completedTasks;completedTasks = ; // ComputedcompletedTasks = ; // Returned from cache
Rememo is published as an npm package:
npm install rememo
Browser-ready versions are available from unpkg. The browser-ready version assigns itself on the global scope as
Rememo's default export is a function:
The returned function is a memoized selector with the following signature:
It's expected that the first argument to the memoized function is the source from which the selector operates. It is ignored when considering whether the argument result has already been cached.
The memoized selector function includes two additional properties:
clear(): When invoked, resets memoization cache.
getDependants( source: Object, ...args: mixed ): The dependants getter for the selector.
getDependants property can be useful when creating selectors which compose other memoized selectors, in which case the dependants are the union of the two selectors' dependants:
const getTasksByCompletion =;const getTasksByCompletionForCurrentDate =;
While designed specifically for use with Redux, Rememo is a simple pattern for efficiently deriving values from any immutable data object. Rememo takes advantage of Redux's core principles of data normalization and immutability. While tracking normalized data in a Redux store is beneficial for eliminating redudancy and reducing overall memory storage, in doing so it sacrifices conveniences that would otherwise make for a pleasant developer experience. It's for this reason that a selector pattern can be desirable. A selector is nothing more than a function which receives the current state and optionally a set of arguments to be used in determining the calculated value.
For example, consider the following state structure to describe a to-do list application:
const state =todo:text: 'Go to the gym' complete: truetext: 'Try to spend time in the sunlight' complete: falsetext: 'Laundry must be done' complete: true;
If we wanted to filter tasks by completion, we could write a simple function:
This works well enough and requires no additional tools, but you'll observe that the filtering we perform on the set of to-do tasks could become costly if we were to have thousands of tasks. And this is just a simple example; real-world use cases could involve far more expensive computation. Add to this the very real likelihood that our application might call this function many times even when our to-do set has not changed.
Furthermore, when used in combination with
connect — which creates pure components by default — it is advisable to pass unchanging object and array references as props on subsequent renders. A selector which returns a new reference on each invocation (as occurs with
Array#filter), your component will needlessly render even if the underlying data does not change.
This is where Rememo comes in: a Rememo selector will cache the resulting value so long as the references upon which it depends have not changed. This works particularly well for immutable data structures, where we can perform a trivial strict equality comparison (
===) to determine whether state has changed. Without guaranteed immutability, equality can only be known by deeply traversing the object structure, an operation which in many cases is far more costly than the original computation.
In our above example, we know the value of the function will only change if the set of to-do's has changed. It's in Rememo's second argument that we describe this dependency:
const getTasksByCompletion =;
Now we can call
getTasksByCompletion as many times as we want without needlessly wasting time filtering tasks when the
todo set has not changed.
To simplify testing of memoized selectors, the function returned by
createSelector includes a
const getTasksByCompletion = ;// Test licecycle management varies by runner. This example uses Mocha.;
Alternatively, you can create separate references (exports) for your memoized and unmemoized selectors, then test only the unmemoized selector.
Refer to Rememo's own tests as an example.
How does this differ from Reselect, another selector memoization library?
Reselect and Rememo largely share the same goals, but have slightly different implementation semantics. Reselect optimizes for function composition, requiring that you pass as arguments functions returning derived data of increasing specificity. Constrasting it to our to-do example above, with Reselect we would pass two arguments: a function which retrieves
todo from the state object, and a second function which receives that set as an argument and performs the completeness filter. The distinction is not as obvious with a simple example like this one, and can be seen more clearly with examples in Reselect's README.
Rememo instead encourages you to consider the derivation first-and-foremost without requiring you to build up the individual dependencies ahead of time. This is especially convenient if your computation depends on many disparate state paths, or if you choose not to memoize all selectors and would rather opt-in to caching at your own judgment. Composing selectors is still straight-forward in Rememo if you subscribe to the convention of passing
state always as the first argument, since this enables your selectors to call upon other each other passing the complete state object.
Copyright 2018 Andrew Duthie
Released under the MIT License.