Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Snyk] Upgrade memoize-one from 5.1.1 to 5.2.1 #42

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dmitrymarokhonov
Copy link

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade memoize-one from 5.1.1 to 5.2.1.

ℹ️ 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.


  • The recommended version is 2 versions ahead of your current version.

  • The recommended version was released 3 years ago, on 2021-04-24.

Release notes
Package name: memoize-one
  • 5.2.1 - 2021-04-24

    The addition of a named import for memoize-one in 5.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 of 5.2.0. 5.2.0 has also been deprecated on npm

  • 5.2.0 - 2021-04-22

    ⚠️ 5.2.0 is deprecated on npm ⚠️

    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

    import memoizeOne from 'memoize-one';

    New feature: Added a named import #37

    DEPRECATED Please continue to use default import

    This resulted in a minor bump for the library

    You can now import memoize-one using a named import if you want

    import { memoizeOne } from 'memoize-one';

    Alternatively, you can continue to use the default import

    import memoizeOne from 'memoize-one';

    Fix: Correctly handling NaN #101

    Our default equality checking function does a === equality check for all arguments. This was problematic when providing special "not a number" numberNaN as NaN !== NaN. Our default equality function now handles NaN values correctly

    Thank 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 of memoize-one to be their latest versions. A reminder that memoize-one has no dependencies 🎉

  • 5.1.1 - 2019-08-23

    Looser EqualityFn type

    For 5.1.0 we shipped an EqualityFn type that was not ideal. It was decided that the simplest path forward for consumers was to move to a looser EqualityFn type. #73

    - export type EqualityFn = (newArgs: readonly unknown[], lastArgs: readonly unknown[]) => boolean;
    + export  type EqualityFn = (newArgs: any[], lastArgs: any[]) => boolean;

    Thanks @ SanderDeWaal1992 for raising this issue

from memoize-one GitHub release notes
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

Note: This is a default PR template raised by Snyk. Find out more about how you can customise Snyk PRs in our documentation.

Snyk has created this PR to upgrade memoize-one from 5.1.1 to 5.2.1.

See this package in npm:
memoize-one

See this project in Snyk:
https://app.snyk.io/org/dmitrymarokhonov/project/337b7583-1d09-4cd5-a2e2-083974685d4b?utm_source=github&utm_medium=referral&page=upgrade-pr
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants