This repository has been archived by the owner on Jan 16, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.0.0
->8.1.1
Release Notes
sindresorhus/mem
v8.1.1
Compare Source
.decorator()
is used (#75)d21357c
v8.1.0
Compare Source
.decorator()
method for TypeScript users (#61)528fa42
v8.0.0
Compare Source
Breaking
0b5c364
The types might be slightly different than v6.
1afa53c
.clear(fn)
if fn’s cache can't be cleared (#59)e7c8893
What happened to v7? This version was prematurely published as v7, so we did v8 to prevent breaking for those already on v7.
v6.1.1
Compare Source
ea88c5c
3ffde5d
v6.1.0
Compare Source
e8bb86c
v6.0.1
Compare Source
809697d
v6.0.0
Compare Source
Breaking
cacheKey
(#43)b7a0766
It now defaults to
cacheKey: x => x
instead of the much more complicated previous default. This means it will now only cache the first argument, and only if it's a primitive. Previously, it tried to cache all arguments usingJSON.stringify()
, but this was both error-prone and slow. This change makes the memoization logic very straightforward, explicit and fast by default. See the readme for how to handle multi-argument or non-primitive value situations.cachePromiseRejection
option (#43)b7a0766
It was not a good fit for
mem
and we plan to add it top-memoize
instead (AddcachePromiseRejection
option sindresorhus/p-memoize#11), which is likemem
, but focused on promises..clear()
is called with a non-memoized function (#44)c73c23b
v5.1.1
Compare Source
1f38c3e
v5.1.0
Compare Source
Enhancements:
c098182
v5.0.0
Compare Source
Breaking:
e54b59b
cachePromiseRejection
option totrue
(#36)70707ae
We decided it's better to default to the least surprising/magic behavior.
Breaking for TypeScript users:
You need to change
import mem from 'mem';
toimport mem = require('mem');
Enhancements:
10f13c0
v4.3.0
Compare Source
9a432b9
298a71e
v4.2.0
Compare Source
6887496
v4.1.0
Compare Source
mimicFn
call (#26)e08ad85
bdfc93a
Configuration
📅 Schedule: "every weekend" in timezone America/Toronto.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻️ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.