内容简介:moizeNOTE: This documentation is for the next major version of
moize
moize
is aconsistently blazing fastmemoization 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.
NOTE: This documentation is for the next major version of moize
, please go to the
v5
branch
to see documentation on the current major version. To learn about changes that may impact your code when migrating to v6, please see the changelog
.
- Configuration options
- Usage with shortcut methods
- Collecting statistics
- Direct cache manipulation
$ npm i moize@next --save
Importing
ESM in browsers
import moize from 'moize';
ESM in NodeJS
import moize from 'moize/mjs/index.mjs';
CommonJS
const moize = require('moize').default;
Usage
import moize from 'moize'; const method = (a: number, b: number) => a + b; const memoized = moize(method); memoized(2, 4); // 6 memoized(2, 4); // 6, pulled from cache
All parameter types are supported, including circular objects, functions, etc. There are also a number ofto memoize for unique use-cases.
Configuration options
moize
optionally accepts an object of options as either the second parameter or as the first step in a curried function:
// inline moize(fn, options); // curried moize(options)(fn);
The full shape of these options:
type Options = { // is the cache based on deep equality of each key argument isDeepEqual: boolean; // is the result a promise isPromise: boolean; // is the result a React component isReact: boolean; // should the parameters be serialized instead of directly referenced isSerialized: boolean; // is the cache based on shallow equality of each key argument isShallowEqual: boolean; // custom method to compare equality between two key arguments matchesArg: (cachedKeyArg: any, keyArg: any) => boolean; // custom method to compare equality across all key arguments matchesKey: (cachedKey: any[], key: any[]) => boolean; // amount of time in milliseconds before the cache will expire maxAge: number; // maximum number of arguments passed to use as key for caching maxArgs: number; // maximum size of cache for this method maxSize: number; // method fired when a new entry is added to cache onCacheAdd: ( cache: moize.Cache, options: moize.Options, moized: (...args: any[]) => any ) => void; // method fire when either a new entry is added to cache or the LRU ordering of the cache has changed onCacheChange: ( cache: moize.Cache, options: moize.Options, moized: (...args: any[]) => any ) => void; // method fired when an existing entry in cache is used onCacheHit: ( cache: moize.Cache, options: moize.Options, moized: (...args: any[]) => any ) => void; // method to fire when a cache entry expires (in combination with maxAge) onExpire: (key: any[]) => void; // the unique identifier to give the memoized method when collecting statistics profileName: string; // method to serialize the arguments to build a unique cache key serializer: (key: any[]) => string; // method to transform the args into a custom format for key storage in cache transformArgs: (key: any[]) => any[]; // should the cache entry's expiration be refreshed when the cache entry is hit (in combination with maxAge) updateExpire: boolean; };
isDeepEqual
defaults to false
Should deep equality be used to compare cache each key argument.
type Arg = { one: { nested: string; }; two: string; }; const fn = ({ one, two }: Arg) => [one, two]; const memoized = moize(fn, { isDeepEqual: true }); memoized({ one: { nested: 'one' }, two: 'two' }); memoized({ one: { nested: 'one' }, two: 'two' }); // pulls from cache
This is also available via the shortcut method of
const memoized = moize.deep(fn);
isPromise
defaults to false
Is the computed value in the function a Promise
.
const fn = async (item: Promise<string>) => await item; const memoized = moize(fn, { isPromise: true });
This is also available via the shortcut method of.
const memoized = -moize.promise(fn);
The Promise
itself will be stored in cache, so that cached returns will always maintain the Promise
contract. For common usage reasons, if the Promise
is rejected, the cache entry will be deleted.
isReact
defaults to false
Is the function passed a stateless functional React
component.
type Props = { one: string; two: number; }; const Component = ({ one, two }: Props) => ( <div> {one}: {two} </div> ); const MemoizedFoo = moize(Component, { isReact: true });
This is also available via the shortcut method of.
const MemoizedFoo = moize.react(Component);
The method will do a shallow equal comparison of both props
and legacy context
of the component based on strict equality. If you want to do a deep equals comparison, setto true.
NOTE: This will memoize on each instance of the component passed, which is equivalent to PureComponent
or React.memo
. If you want to
memoize on all
instances (which is how this option worked prior to version 6), use the following options:
const memoized = moize(Component, { isShallowEqual: true, maxArgs: 2 });
isSerialized
defaults to false
Serializes the parameters passed into a string and uses this as the key for cache comparison.
const fn = (mutableObject: { one: Record<string, any> }) => mutableObject.property; const memoized = moize(fn, { isSerialized: true });
This is also available via the shortcut method of.
const memoized = moize.serialize(fn);
If serialize
is combined with either maxArgs
or transformArgs
, the following order is used:
maxArgs transformArgs serializer
NOTE: This is much slower than the default key storage, and usually the same requirements can be meet with isDeepEqual
, so use at your discretion.
isShallowEqual
defaults to false
Should shallow equality be used to compare cache each key argument.
type Arg = { one: string; two: string; }; const fn = ({ one, two }: Arg) => [one, two]; const memoized = moize(fn, { isDeepEqual: true }); memoized({ one: 'one', two: 'two' }); memoized({ one: 'one', two: 'two' }); // pulls from cache
This is also available via the shortcut method of
const memoized = moize.shallow(fn);
matchesArg
defaults to SameValueZero equality
Custom method used to compare equality of keys for cache purposes by comparing each argument.
type Arg = { one: string; two: string; }; const fn = ({ one, two }: Arg) => [one, two]; const hasOneProperty = (cacheKeyArg: Arg, keyArg: Arg) => Object.keys(cacheKeyArg).length === 1 && Object.keys(keyArg).length === 1; const memoized = moize(fn, { matchesArg: hasOneProperty }); memoized({ one: 'two' }; memoized({ two: 'three' }); // pulls from cache
This is also available via the shortcut method of
const memoized = moize.matchesArg(hasOneProperty)(fn);
NOTE: This comparison is used iteratively on each argument, rather than comparing the two keys as a whole. If you want to compare the key as a whole, you should use.
matchesKey
Custom method used to compare equality of keys for cache purposes by comparing the entire key.
type Arg = { one: string; two: string; }; const fn = ({ one, two }: Arg) => [one, two]; const isFooEqualAndHasBar = (cacheKey: [Arg], key: [Arg]) => cacheKey[0].one === key[0].one && cacheKey[1].hasOwnProperty('two') && key[1].hasOwnProperty('two'); const memoized = moize(fn, { matchesKey: isFooEqualAndHasBar }); memoized({ one: 'two' }, { two: null }); memoized({ one: 'two' }, { two: 'three' }); // pulls from cache
This is also available via the shortcut method of
const memoized = moize.matchesKey(isFooEqualAndHasBar)(fn);
NOTE: This comparison uses the two keys as a whole, which is usually less performant than the matchArg
comparison used iteratively on each argument. Generally speaking you should use theoption for equality comparison.
maxAge
The maximum amount of time in milliseconds that you want a computed value to be stored in cache for this method.
const fn = (item: Record<string, any>) => item; const MAX_AGE = 1000 * 60 * 5; // five minutes; const memoized = moize(fn, { maxAge: MAX_AGE });
This is also available via the shortcut method of.
const memoized = moize.maxAge(MAX_AGE)(fn);
TIP: A common usage of this is in tandom with isPromise
for AJAX calls, and in that scenario the expected behavior is usually to have the maxAge
countdown begin upon resolution of the promise. If this is your intended use case, you should also apply the updateExpire
option.
maxArgs
The maximum number of arguments (starting from the first) used in creating the key for the cache.
const fn = (item1: string, item2: string, item3: string) => item1 + item2 + item3; const memoized = moize(fn, { maxArgs: 2 }); memoize('one', 'two', 'three'); memoize('one', 'two', 'four'); // pulls from cache, as the first two args are the same
This is also available via the shortcut method of.
const memoized = moize.maxArgs(2)(fn);
If maxArgs
is combined with either serialize
or transformArgs
, the following order is used:
maxArgs transformArgs serializer
maxSize
defaults to Infinity
The maximum number of values you want stored in cache for this method. Clearance of the cache once the maxSize
is reached is on a Least Recently Used
basis.
const fn = (item: string) => item; const memoized = moize(fn, { maxSize: 5 });
This is also available via the shortcut method of.
const memoized = moize.maxSize(5)(fn);
onCacheAdd
Method to fire when an item has been added to cache. Receives the cache, options, and memoized function as a parameters.
const fn = (one: string, two: string) => [one, two]; const logCacheKeys = ( cache: Cache, options: Options, moized: Moized<typeof fn> ) => console.log(cache.keys); const moized = moize(fn, { maxSize: 2, onCacheAdd: logCacheKeys }); moized('one', 'two'); // [["one","two"]] moized('one', 'two'); moized('two', 'one'); // [["two","one"], ["one","two"]] moized('one', 'two');
NOTE: When combined with onCacheChange
, this method will always fire first.
onCacheChange
Method to fire when an item has been either added to cache, or existing cache was reordered based on a cache hit. Receives the cache, options, and memoized function as a parameters.
const fn = (one: string, two: string) => [one, two]; const logCacheKeys = ( cache: Cache, options: Options, moized: Moized<typeof fn> ) => console.log(cache.keys); const moized = moize(fn, { maxSize: 2, onCacheChange: logCacheKeys }); moized('one', 'two'); // [["one","two"]] moized('one', 'two'); moized('two', 'one'); // [["two","one"], ["one","two"]] moized('one', 'two'); // [["one","two"], ["two","one"]]
NOTE: When combined with onCacheAdd
or onCacheHit
, this method will always fire last.
onCacheHit
Method to fire when an existing cache item is found. Receives the cache, options, and memoized function as a parameters.
const fn = (one: string, two: string) => [one, two]; const logCacheKeys = ( cache: Cache, options: Options, moized: Moized<typeof fn> ) => console.log(cache.keys); const moized = moize(fn, { maxSize: 2, onCacheHit: logCacheKeys }); moized('one', 'two'); moized('one', 'two'); // [["one","two"]] moized('two', 'one'); moized('one', 'two'); // [["two","one"], ["one","two"]]
NOTE: When combined with onCacheChange
, this method will always fire first.
onExpire
A callback that is called when the cached entry expires.
const fn = (item: string) => item; const logKey = (key: Key<string>) => console.log(key); const memoized = moize(fn, { maxAge: 10000, onExpire: logKey });
If you return false
from this method, it will prevent the key's removal and refresh the expiration in the same vein as updateExpire
based on maxAge
:
const fn = (item: string) => item; let expirationAttempts = 0; const limitExpirationAttempts = (key: Key<string>) => { expirationAttempts += 1; return expirationAttempts < 2; }; const memoized = moize(fn, { maxAge: 10000, onExpire: limitExpirationAttempts, }); memoized('one'); // will expire key after 30 seconds, or 3 expiration attempts
NOTE: You must set afor this option to take effect.
profileName
defaults to function name and file/line location
Name to use as unique identifier for the function when collecting statistics.
moize.collectStats(); const fn = (item: string) => item; const memoized = moize(fn, { profileName: 'my fancy identity' });
This is also available via the shortcut method of.
const memoized = moize.profile('profile-name')(fn);
NOTE: You must be collecting statistics for this option to take effect.
serializer
defaults to serializeArguments in utils.js
Method used in place of the internal serializer when serializing the parameters for cache key comparison. The function accepts a single argument, the Array
of args
, and must also return an Array
.
const fn = (one: string, two: string) => [one, two]; const customSerializer = (args: string[]) => [JSON.stringify(args[0])]; const memoized = moize(fn, { isSerialized: true, serializer, });
This is also available via the shortcut method of.
const memoized = moize.serializeWith(customSerializer)(fn);
NOTE: You must setfor this option to take effect.
transformArgs
Transform the arguments passed before it is used as a key. The function accepts a single argument, the Array
of args
, and must also return an Array
.
const fn = (one: string | null, two: string | null, three: string | null) => [ two, three, ]; const ignoreFirstArg = (args: (string | null)[]) => args.slice(1); const moized = moize(fn, { transformArgs: ignoreFirstArg }); moize('one', 'two', 'three'); moize(null, 'two', 'three'); // pulled from cache
This is also available via the shortcut method of.
const memoized = moize.transformArgs(argTransformer)(fn);
If transformArgs
is combined with either maxArgs
or serialize
, the following order is used:
maxArgs transformArgs serializer
updateExpire
When a maxAge
is set, clear the scheduled expiration of the key when that key is retrieved, setting a new expiration based on the most recent retrieval from cache.
const fn = (item: string) => item; const MAX_AGE = 1000 * 60 * 5; // five minutes const memoized = moize(fn, { maxAge: MAX_AGE, updateExpire: true }); memoized('one'); setTimeout(() => { /** * hits cache, which updates the expire to be 5 minutes * from this run instead of the first */ memoized('one'); }, 1000 * 60);
Usage with shortcut methods
moize.deep
Pre-applies theoption.
import moize from 'moize'; const fn = (one: string, two: string) => `${one} ${two}`; export default moize.deep(fn);
moize.infinite
Pre-applies theoption with Infinity
.
import moize from 'moize'; const fn = (one: string, two: string) => `${one} ${two}`; export default moize.infinite(fn);
NOTE: This mimics default behavior of moize
prior to version 6.
moize.matchesArg
Pre-applies theoption as a curriable method.
import moize from 'moize'; const isEqualOrFoo = (cacheKeyArg: string, keyArg: string) => cacheKeyArg === keyArg || keyArg === 'one'; const fn = (one: string, two: string) => `${one} ${two}`; export default moize.matchesArg(isEqualOrFoo)(fn);
moize.matchesKey
Pre-applies theoption as a curriable method.
import moize from 'moize'; const fn = (one: string, two: string) => `${one} ${two}`; const isEqualOrHasFoo = (cacheKey: Key<string>, key: Key<string>) => key.every((keyArg, index) => keyArg === cacheKey[index]) || key.some((keyArg) => keyArg === 'one'); export default moize.matchesKey(isEqualOrHasFoo)(fn);
moize.maxAge
Pre-applies theoption as a curriable method.
import moize from 'moize'; const fn = (one: string, two: string) => `${one} ${two}`; export default moize.maxAge(5000)(fn);
moize.maxArgs
Pre-applies theoption as a curriable method.
import moize from 'moize'; const fn = (one: string, two: string) => `${one} ${two}`; export default moize.maxArgs(1)(fn);
moize.maxSize
Pre-applies theoption as a curriable method.
import moize from 'moize'; const fn = (one: string, two: string) => `${one} ${two}`; export default moize.maxSize(5)(fn);
moize.promise
Pre-applies theandoptions. The updateExpire
option does nothing ifis not also applied, but ensures that the expiration begins at the resolution of the promise rather than the instantiation of it.
import moize from 'moize'; const fn = async (one: string, two: Record<string, any>) => await someApiCall(one, two); export default moize.promise(fn);
NOTE: If you do not want the promise to update its expiration when the cache is hit, then you should use the isPromise
option directly instead.
moize.react
Pre-applies the) option for memoizing functional components in React
. Key
comparisons are based on a shallow equal comparison of both props and legacy context.
import moize from 'moize'; type Props = { one: string; two: number; }; const Component = ({ one, two }: Props) => ( <div> {one} {two} </div> ); export default moize.react(Component);
NOTE: This method will not operate with components made via the class
instantiation, as they do not offer the same referential transparency
.
moize.serialize
Pre-applies theoption.
import moize from 'moize'; const fn = (one: Record<string, any>, two: Record<string, any>) => ({ one, two, }); export default moize.serialize(fn);
NOTE: If you want to provide a custom, you should use:
moize.serializeWith(customSerializer)(fn);
moize.serializeWith
Pre-applies theandoptions.
import moize from 'moize'; const fn = (one: Record<string, any>, two: Record<string, any>) => ({ one, two, }); export default moize.serializeWith(JSON.stringify)(fn);
NOTE: If you want to use the default, you should use moize.serialize
:
moize.serializeWith(customSerializer)(fn);
moize.shallow
Pre-applies theoption.
import moize from 'moize'; const fn = (one: string, two: string) => `${one} ${two}`; export default moize.shallow(fn);
useMoize hook
If you are using React 16.8+ and are using hooks, you can easily create a custom useMoize
hook for your project:
import { useRef } from 'react'; export function useMoize(fn, args, options) { const moizedFnRef = useRef(moize(fn, options)); return moizedFnRef.current(...args); }
Which can then be used as such:
import React from 'react'; import { useMoize } from './moize-hooks'; function MyComponent({ first, second, object }) { // standard usage const sum = useMoize((a, b) => a + b, [first, second]); // with options const deepSum = useMoize((obj) => obj.a + obj.b, [object], { isDeepEqual: true, }); return ( <div> Sum of {first} and {second} is {sum}. Sum of {object.a} and{' '} {object.b} is {deepSum}. </div> ); }
Naturally you can tweak as needed for your project (default options, option-specific hooks, etc).
NOTE: This is very similar to
useCallback
built-in hook, with two main differences:
-
There is a third parameter passed (thepassed to
moize
) - The second argument array is the list of arguments passed to the memoized function
In both useCallback
and useMemo
, the array is a list of dependencies
which determine whether the funciton is called. These can be different than the arguments, although in general practice they are equivalent. The decision to use them directly was both for this common use-case reasons, but also because the implementation complexity would have increased substantially if not.
Composition
Starting with version 2.3.0
, you can compose moize
methods. This will create a new memoized method with the original function that shallowly merges the options of the two setups. Example:
import moize from 'moize'; const Component = (props: Record<string, any>) => <div {...props} />; // memoizing with react, as since 2.0.0 const MemoizedFoo = moize.react(Component); // creating a separately-memoized method that has maxSize of 5 const LastFiveFoo = moize.maxSize(5)(MemoizedFoo);
You can also create an options-first curriable version of moize
if you only pass the options:
import moize from 'moize'; // creates a function that will memoize what is passed const limitedSerializedMoize = moize({ maxSize: 5, serialize: true }); const getWord = (bird) => `${bird} is the word`; const moizedGetWord = limitedSerializedMoize(getWord);
You can also combine all of these options with moize.compose
to create moize
wrappers with pre-defined options.
import moize from 'moize'; // creates a moizer that will have the options of // {isReact: true, maxAge: 5000, maxSize: 5} const superLimitedReactMoize = moize.compose( moize.react, moize.maxSize(5), moize.maxAge(5000) );
Collecting statistics
As-of version 5, you can collect statistics of moize to determine if your cached methods are effective.
import moize from 'moize'; moize.collectStats(); const fn = (one: string, two: string) => [one, two]; const moized = moize(fn); moized('one', 'two'); moized('one', 'two'); moized.getStats(); // {"calls": 2, "hits": 1, "usage": "50%"}
NOTE: It is recommended not to activate this in production, as it will have a performance decrease.
Stats methods
clearStats
Cear statistics on moize
d functions.
moize.clearStats(); // clears all stats moize.clearStats('profile-name'); // clears stats only for 'profile-name'
collectStats
Set whether collecting statistics on moize
d functions.
moize.collectStats(true); // start collecting stats moize.collectStats(); // same as passing true moize.collectStats(false); // stop collecting stats
getStats([profileName])
Get the statistics for a specific function, or globally.
moize.collectStats(); const fn = (one: string, two: string) => [one, two]; const moized = moize(fn); const otherFn = (one: string[]) => one.slice(0, 1); const otherMoized = moize(otherFn, { profileName: 'otherMoized' }); moized('one', 'two'); moized('one', 'two'); moized.getStats(); // {"calls": 2, "hits": 1, "usage": "50%"} otherMoized(['three']); moize.getStats('otherMoized'); // {"calls": 1, "hits": 0, "usage": "0%"} moize.getStats(); /* { "calls": 3, "hits": 1, "profiles": { "fn at Object..src/utils.js (http://localhost:3000/app.js:153:68)": { "calls": 2, "hits": 1, "usage": "50%" }, "otherMoized": { "calls": 1, "hits": 0, "usage": "0%" } }, "usage": "33.3333%" } */
Introspection
isCollectingStats
Are statistics being collected on memoization usage.
moize.collectStats(true); moize.isCollectingStats(); // true moize.collectStats(false); moize.isCollectingStats(); // false
isMoized
Is the function passed a moized function.
const fn = () => {}; const moizedFn = moize(fn); moize.isMoized(fn); // false moize.isMoized(moizedFn); // true
Direct cache manipulation
The cache is available on the moize
d function as a property, and while it is not recommended to modify it directly, that option is available for edge cases.
cache
The shape of the cache
is as follows:
type Cache = { keys: any[][]; size: number; values: any[]; };
Regardless of how the key is transformed, it is always stored as an array (if the value returned is not an array, it is coalesced to one).
NOTE: The order of keys
and values
should always align, so be aware when manually manipulating the cache that you need to manually keep in sync any changes to those arrays.
cacheSnapshot
The cache
is mutated internally for performance reasons, so logging out the cache at a specific step in the workflow may not give you the information you need. As such, to help with debugging you can request the cacheSnapshot
, which has the same shape as the cache
but is a shallow clone of each property for persistence.
There are also convenience methods provided on the moize
d function which allow for programmatic manipulation of the cache.
add(key, value)
This will manually add the value
at key
in cache if key
does not already exist. key
should be an Array
of values, meant to reflect the arguments passed to the method.
// single parameter is straightforward const memoized = moize((item: string) => item: string); memoized.add(['one'], 'two'); // pulls from cache memoized('one');
NOTE: This will only add key
s that do not exist in the cache, and will do nothing if the key
already exists. If you want to update keys that already exist, use.
clear()
This will clear all values in the cache, resetting it to an empty state.
const memoized = moize((item: string) => item); memoized.clear();
get(key)
Returns the value in cache if the key matches, else returns undefined
. key
should be an Array
of values, meant to reflect the arguments passed to the method.
const memoized = moize((one: string, two: string) => [one, two); memoized('one', 'two'); console.log(memoized.get(['one', 'two'])); // ["one","two"] console.log(memoized.get(['two', 'three'])); // undefined
getStats()
Returns the statistics for the function.
moize.collectStats(); const memoized = moize((one: string, two: string) => [one, two); memoized('one', 'two'); memoized('one', 'two'); console.log(memoized.getStats()); // {"calls": 2, "hits": 1, "usage": "50%"}
NOTE: You must be collecting statistics for this to be populated.
has(key)
This will return true
if a cache entry exists for the key
passed, else will return false
. key
should be an Array
of values, meant to reflect the arguments passed to the method.
const memoized = moize((one: string, two: string) => [one, two]); memoized('one', 'two'); console.log(memoized.has(['one', 'two'])); // true console.log(memoized.has(['two', 'three'])); // false
keys()
This will return a list of the current keys in cache
.
const memoized = moize.maxSize(2)((item: any) => item); memoized('one'); memoized({ two: 'three' }); const keys = memoized.keys(); // [['one'], [{two: 'three'}]]
remove(key)
This will remove the provided key
from cache. key
should be an Array
of values, meant to reflect the arguments passed to the method.
const memoized = moize((item: { one: string }) => item); const arg = { one: 'one' }; memoized(arg); memoized.remove([arg]); // will re-execute, as it is no longer in cache memoized(arg);
NOTE: This will only remove key
s that exist in the cache, and will do nothing if the key
does not exist.
update(key, value)
This will manually update the value
at key
in cache if key
exists. key
should be an Array
of values, meant to reflect the arguments passed to the method.
// single parameter is straightforward const memoized = moize((item: string) => item); memoized.add(['one'], 'two'); // pulls from cache memoized('one');
NOTE: This will only update key
s that exist in the cache, and will do nothing if the key
does not exist. If you want to add keys that do not already exist, use.
values()
This will return a list of the current values in cache
.
const memoized = moize.maxSize(2)((item: string | { two: string }) => ({ item, })); memoized('one'); memoized({ two: 'three' }); const values = memoized.values(); // [{item: 'one'}, {item: {two: 'three'}}]
Benchmarks
All values provided are the number of operations per second calculated by the Benchmark suite
, where a higher value is better. Each benchmark was performed using the default configuration of the library, with a fibonacci calculation based on a starting parameter of 35
, using single and multiple parameters with different object types. The results were averaged to determine overall speed across possible usage.
NOTE: lodash
, ramda
, and underscore
do not support mulitple-parameter memoization without use of a resolver
function. For consistency in comparison, each use the same resolver
that returns the result of JSON.stringify
on the arguments.
Name | Overall (average) | Single (average) | Multiple (average) | single primitive | single array | single object | multiple primitive | multiple array | multiple object |
---|---|---|---|---|---|---|---|---|---|
moize | 91,802,487 | 122,870,101 | 60,734,874 | 139,060,583 | 115,051,924 | 114,497,797 | 63,517,382 | 57,770,352 | 60,916,888 |
mem | 79,716,851 | 79,834,031 | 79,599,672 | 128,222,483 | 56,245,856 | 55,033,755 | 129,202,586 | 54,522,582 | 55,073,849 |
lru-memoize | 56,821,369 | 70,091,175 | 43,551,563 | 77,843,255 | 65,753,790 | 66,676,480 | 41,949,360 | 42,772,024 | 45,933,307 |
fast-memoize | 33,055,406 | 64,774,644 | 1,336,169 | 190,041,355 | 2,316,045 | 1,966,532 | 1,775,305 | 1,246,369 | 986,835 |
lodash | 28,468,492 | 55,472,191 | 1,464,793 | 66,618,867 | 50,846,997 | 48,950,709 | 1,942,482 | 1,408,940 | 1,042,957 |
memoizee | 23,694,567 | 29,635,411 | 17,753,722 | 28,972,019 | 30,544,377 | 29,389,838 | 17,213,582 | 17,816,727 | 18,230,859 |
ramda | 19,084,317 | 36,523,277 | 1,645,357 | 103,180,140 | 1,898,359 | 4,491,334 | 2,171,391 | 1,619,360 | 1,145,320 |
underscore | 8,068,290 | 14,476,359 | 1,660,221 | 26,864,965 | 4,356,018 | 12,208,096 | 2,192,586 | 1,633,516 | 1,154,562 |
memoizerific | 7,267,897 | 8,101,327 | 6,434,466 | 8,311,252 | 8,084,237 | 7,908,494 | 6,276,233 | 6,661,302 | 6,365,865 |
addy-osmani | 5,060,196 | 6,565,536 | 3,554,857 | 12,898,869 | 3,922,517 | 2,875,224 | 6,972,596 | 2,069,750 | 1,622,225 |
Filesize
moize
is fairly small (about 4.5KB when minified and gzipped), however it provides a large number of configuration options to satisfy a number of edge cases. If filesize is a concern, you may consider using
micro-memoize
. This is the memoization library that powers moize
under-the-hood, and will handle most common use cases at 1/4 the size of moize
.
Browser support
- Chrome (all versions)
- Firefox (all versions)
- Edge (all versions)
- Opera 15+
- IE 9+
- Safari 6+
- iOS 8+
- Android 4+
Development
Standard stuff, clone the repo and npm install
dependencies. The npm scripts available:
-
benchmark
=> run the benchmark suite pittingmoize
against other libraries in common use-cases -
benchmark:alternative
=> run the benchmark suite for alternative forms of caching -
benchmark:array
=> run the benchmark suite for memoized methods using single and multiplearray
parameters -
benchmark:object
=> run the benchmark suite for memoized methods using single and multipleobject
parameters -
benchmark:primitive
=> run the benchmark suite for memoized methods using single and multipleobject
parameters -
benchmark:react
=> run the benchmark suite for memoized React components -
build
=> run rollup to build the distributed files indist
-
clean:dist
=> runrimraf
on thedist
folder -
clean:docs
=> runrimraf
on thedocs
folder -
clean:mjs
=> runrimraf
on themjs
folder -
copy:mjs
=> runclean:mjs
and thees-to-mjs
script -
copy:types
=> copy internal types to be available for consumer -
dev
=> run webpack dev server to run example app (playground!) -
dist
=> runsclean:dist
andbuild
-
docs
=> runsclean:docs
and builds the docs viajsdoc
-
flow
=> runsflow check
on the files insrc
-
lint
=> runs ESLint against all files in thesrc
folder -
lint:fix
=> runs `lint``, fixing any errors if possible -
test
=> runjest
test functions withNODE_ENV=test
-
test:coverage
=> runtest
but with code coverage -
test:watch
=> runtest
, but with persistent watcher -
typecheck
=> runtsc
against source code to validate TypeScript
以上所述就是小编给大家介绍的《moize 6 now in beta》,希望对大家有所帮助,如果大家有任何疑问请给我留言,小编会及时回复大家的。在此也非常感谢大家对 码农网 的支持!
猜你喜欢:本站部分资源来源于网络,本站转载出于传递更多信息之目的,版权归原作者或者来源机构所有,如转载稿涉及版权问题,请联系我们。
Mathematica Cookbook
Sal Mangano / O'Reilly Media / 2009 / GBP 51.99
As the leading software application for symbolic mathematics, Mathematica is standard in many environments that rely on math, such as science, engineering, financial analysis, software development, an......一起来看看 《Mathematica Cookbook》 这本书的介绍吧!