[Snyk] Upgrade memoize-one from 5.0.0 to 6.0.0 #32
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.
Snyk has created this PR to upgrade memoize-one from 5.0.0 to 6.0.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Warning: This is a major version upgrade, and may be a breaking change.
Release notes
Package name: memoize-one
Read more
v6.0.0-beta.1
The addition of a named import for
memoize-one
in5.2.0
created an unintentional breaking change for our CommonJS bundle #116 (Thanks @ ehmicky for finding this)5.2.1
reverts the addition of the named import of5.2.0
.5.2.0
has also been deprecated onnpm
5.2.0
is deprecated onnpm
The addition of our named import created a breaking change for our CommonJS build #116 (Thanks @ ehmicky for finding this)
The named import feature has been reverted and you can continue to use the default import has you always have
New feature: Added a named import #37
You can now import
memoize-one
using a named import if you wantAlternatively, you can continue to use the default import
Fix: Correctly handling
NaN
#101Our default equality checking function does a
===
equality check for all arguments. This was problematic when providing special "not a number"number
→NaN
asNaN
!==NaN
. Our default equality function now handlesNaN
values correctlyThank you @ ohoho7 for raising this and @ Ayub-Begimkulov for diving it forward
Improvement: Documentation
I have added more detail to the readme which explains in greater detail how our default equality function works
Improvement: Bumping dev dependencies
I have upgraded all the
devDependencies
ofmemoize-one
to be their latest versions. A reminder thatmemoize-one
has nodependencies
🎉Looser
EqualityFn
typeFor
5.1.0
we shipped anEqualityFn
type that was not ideal. It was decided that the simplest path forward for consumers was to move to a looserEqualityFn
type. #73Thanks @ SanderDeWaal1992 for raising this issue
Typescript
support! 🤘🤩🤘Typescript
consumers will now start getting correct types without having to rely on installing@ types/memoize-one
. Internallymemoize-one
is now authored inTypescript
.memoize-one
is still shippingflow
types, so if you are using, or want to useflow
, then you will still get the same fantastic types you always have.And if you want to use good old regular vanilla JS then you can do that too!
❤ Thanks to @ PavelVanecekAtlassian, @ danieldelcore and @ TrySound for their assistance. And thanks to @ karol-majewski and @ franklixuefei for creating the previous
memoize-one
typescript
types on DefinitelyTypedv5.1.0-beta.6
v5.1.0-beta.5
v5.1.0-beta.4
v5.1.0-beta.3
Commit messages
Package name: memoize-one
Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs