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

Update dependency mem to v10 - autoclosed #54

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 20, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
mem 5.1.1 -> 10.0.0 age adoption passing confidence

Release Notes

sindresorhus/mem (mem)

v10.0.0

Compare Source

Breaking
  • Rename package from mem to memoize 4756892
  • Require Node.js 18 3afdfaf
  • Renamed the memDecorator named import to memoizeDecorator 4756892
  • Renamed the memClear named import to memoizeClear 4756892

v9.0.2

Compare Source

v9.0.1

Compare Source

  • Fix using multiple decorators on the same instance (#​78) 7f7ca0a

v9.0.0

Compare Source

Breaking

v8.1.1

Compare Source

  • Don't use the same memoized function across instances when .decorator() is used (#​75) d21357c

v8.1.0

Compare Source

v8.0.0

Compare Source

Breaking
  • Convert the package to TypeScript (#​64) 0b5c364
    The types might be slightly different than v6.
  • Require Node.js 10 (#​67) 1afa53c
  • Throw on .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

v6.1.0

Compare Source

v6.0.1

Compare Source

  • Support overloaded functions (TypeScript types) (#​48) 809697d

v6.0.0

Compare Source

Breaking
  • Simplify the default 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 using JSON.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.
  • Drop the cachePromiseRejection option (#​43) b7a0766
    It was not a good fit for mem and we plan to add it to p-memoize instead (https://github.com/sindresorhus/p-memoize/issues/11), which is like mem, but focused on promises.
  • Throw when .clear() is called with a non-memoized function (#​44) c73c23b

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update dependency mem to v10 Update dependency mem to v10 - autoclosed Aug 6, 2024
@renovate renovate bot closed this Aug 6, 2024
@renovate renovate bot deleted the renovate/mem-10.x branch August 6, 2024 08:09
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.

0 participants