Displaying 1 to 20 from 24 results

fast-memoize.js - :rabbit2: Fastest possible memoization library

  •    Javascript

This library is an attempt to make the fastest possible memoization library in JavaScript that supports N arguments. The fastest cache is used for the running environment, but it is possible to pass a custom cache to be used.

memoize-one - A memoization library which only remembers the latest invocation

  •    Javascript

A memoization library that only caches the result of the most recent arguments. There are only two hard things in Computer Science: cache invalidation and naming things.

memoizee - Complete memoize/cache solution for JavaScript

  •    Javascript

Originally derived from es5-ext package. memoize name was already taken, therefore project is published as memoizee on NPM.




moize - The consistently-fast, complete memoization solution for JS

  •    Javascript

moize is a consistently blazing fast memoization library for JavaScript. It handles multiple parameters (including default values) without any additional configuration, and offers a large number of options to satisfy any number of potential use-cases. All parameter types are supported, including circular objects, functions, etc. There are also a number of shortcut methods to memoize for unique use-cases.


disk-memoizer - Simple disk memoization for caching hight latency IO responses

  •    Javascript

Simple disk memoization and in memory LRU cache for speeding up frequently accessed high latency IO resources. Queues up concurrent requests for the same resource before it has been cached to avoid fetching it multiple times in parallel.

memo-it - :inbox_tray: :outbox_tray: simple yet clever memoization helper with parameter support

  •    Ruby

Clever memoization helper that uses Ruby internals instead of meta-programming.

memoize.js - A faster JavaScript memoizer

  •    Javascript

Whilst not new by any means, memoization is a useful optimization technique for caching the results of function calls such that lengthy lookups or expensive recursive computations can be minimized where possible. The basic idea is that if you can detect an operation has already been previously completed for a specific set of input values, the stored result can instead be returned instead of repeating the operation again.

memo-decorator - Decorator which applies memoization to a method of a class.

  •    TypeScript

This decorator applies memoization to a method of a class. Apply the decorator to a method of a class. The cache is local for the method but shared among all instances of the class. Strongly recommend you to use this decorator only on pure methods.

memoizerific - Fast, small, efficient JavaScript memoization lib to memoize JS functions.

  •    Javascript

Fast (see benchmarks), small (1k min/gzip), efficient, JavaScript memoization lib to memoize JS functions. Uses JavaScript's Map() object for instant lookups, or a performant polyfill if Map is not available - does not do expensive serialization or string manipulation.

beautiful-react-redux - Redux 🚀, Redux 🤘, Redux 🔥

  •    Javascript

Automagically enhances, even enchants redux connect, to be more concrete - mapStateToProps, wrapping it with memoize-state to sky-rocket your application. Just import beautiful-react-redux and forget about reselect and any other selector memoization. Now your application will runs like it has MobX underneath.

memoize-state - The magic memoization for the State management. ✨🧠

  •    Javascript

Reselect? Memoize-one? Most of memoization libraries remembers the parameters you provided, not what you did inside. Sometimes is not easy to achive high cache hit ratio. Sometimes you have to think about how to properly dissolve computation into the memoizable parts. Memoize-state is built to memoize more complex situations, even the ones which are faster to recomoute, than to deside that recalculation is not needed. Just because one cheap computation can cause a redraw/reflow/recomputation cascade for a whole application.

why-did-you-update-redux - Patch Redux to discover unnecessary re-renders

  •    Javascript

Why did you update is a function that monkey patches Redux and notifies you in the console when potentially unnecessary re-renders occur due to a unnecessary update from mapStateToProps. This library is available on npm, install it with: npm install --save why-did-you-update-redux or yarn add why-did-you-update-redux.