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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The version 4.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of memoize-one.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes4.0.0
Changes
A bundle of joy 🎁
We are now publishing a number of bundle builds for your consumption needs!
Previously if your result function threw a value you could get some strange behaviour. We have fixed this so that memoizeOne is aware when your result function throws a value. If your result function throws then the memoized function will also throw. A thrown value is not cached and the result function will be re-executed if called again with the same arguments.
try { memoized('first message'); // console.log => 'first message' // even though the arguments are the same the result function was called again
} catch (e) {
secondError = e;
}
// result is regenerated and not cached console.log(firstError === secondError); // false
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.
Version 4.0.0 of memoize-one was just published.
The version 4.0.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of memoize-one.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
4.0.0Changes
A bundle of joy 🎁
We are now publishing a number of bundle builds for your consumption needs!
dist/memoize-one.cjs.js
CommonJS bundledist/memoize-one.esm.js
ESM bundledist/memoize-one.min.js
UMD bundle (production build)dist/memoize-one.js
UMD bundle (development build)Bumping
flow
We are now on the latest version of
flow
:0.75
.Commits
The new version differs by 5 commits.
3fe7a61
v4.0.0
1eac004
Bundle of love. Closes #24 (#25)
2739329
Update README.md
1a218e3
Update README.md
91712c6
Update README.md
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴