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

fix(deps): update dependency lru-cache to v9 #468

Merged
merged 7 commits into from
May 17, 2023
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 10, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
lru-cache ^6.0.0 -> ^9.0.0 age adoption passing confidence

Release Notes

isaacs/node-lru-cache

v9.1.0

Compare Source

  • cache.set(key, undefined) is now an alias for
    cache.delete(key)

v9.0.3

Compare Source

v9.0.2

Compare Source

v9.0.1

Compare Source

v9.0.0

Compare Source

  • Use named export only, no default export.

v8.0.5

Compare Source

v8.0.4

Compare Source

v8.0.3

Compare Source

v8.0.2

Compare Source

v8.0.1

Compare Source

v8.0.0

Compare Source

  • The fetchContext option was renamed to context, and may no
    longer be set on the cache instance itself.
  • Rewritten in TypeScript, so pretty much all the types moved
    around a lot.
  • The AbortController/AbortSignal polyfill is removed. For this
    reason, Node version 16.14.0 or higher is now required.
  • Internal properties were moved to actual private class
    properties.
  • Keys and values must not be null or undefined.
  • Minified export available at 'lru-cache/min', for both CJS
    and MJS builds.

v7.18.3

Compare Source

v7.18.2

Compare Source

v7.18.1

Compare Source

v7.18.0

Compare Source

  • Add support for internal state investigation through the use of
    a status option to has(), set(), get(), and fetch().

v7.17.2

Compare Source

v7.17.1

Compare Source

v7.17.0

Compare Source

  • Add signal option for fetch to pass a user-supplied
    AbortSignal
  • Add ignoreFetchAbort and allowStaleOnFetchAbort options

v7.16.2

Compare Source

  • Fail fetch() promises when they are aborted

v7.16.1

Compare Source

v7.16.0

Compare Source

  • Add allowStaleOnFetchRejection option

v7.15.0

Compare Source

  • Provide both ESM and CommonJS exports

v7.14.1

Compare Source

v7.14.0

Compare Source

  • Add maxEntrySize option to prevent caching items above a
    given calculated size.

v7.13.2

Compare Source

v7.13.1

Compare Source

v7.13.0

Compare Source

  • Add forceRefresh option to trigger a call to the
    fetchMethod even if the item is found in cache, and not
    older than its ttl.

v7.12.1

Compare Source

v7.12.0

Compare Source

  • Add fetchContext option to provide additional information to
    the fetchMethod
  • 7.12.1: Fix bug where adding an item with size greater than
    maxSize would cause bizarre behavior.

v7.11.0

Compare Source

  • Add 'noDeleteOnStaleGet' option, to suppress behavior where a
    get() of a stale item would remove it from the cache.

v7.10.3

Compare Source

v7.10.2

Compare Source

v7.10.1

Compare Source

v7.10.0

Compare Source

  • Add noDeleteOnFetchRejection option, to suppress behavior
    where a failed fetch will delete a previous stale value.
  • Ship types along with the package, rather than relying on
    out of date types coming from DefinitelyTyped.

v7.9.1

Compare Source

v7.9.0

Compare Source

  • Better AbortController polyfill, supporting
    signal.addEventListener('abort') and signal.onabort.
  • (7.9.1) Drop item from cache instead of crashing with an
    unhandledRejection when the fetchMethod throws an error or
    returns a rejected Promise.

v7.8.2

Compare Source

v7.8.1

Compare Source

v7.8.0

Compare Source

  • add updateAgeOnHas option
  • warnings sent to console.error if process.emitWarning unavailable

v7.7.4

Compare Source

v7.7.3

Compare Source

v7.7.2

Compare Source

v7.7.1

Compare Source

v7.7.0

Compare Source

  • fetch: provide options and abort signal

v7.6.1

Compare Source

v7.6.0

Compare Source

  • add cache.getRemainingTTL(key)
  • Add async cache.fetch() method, fetchMethod option
  • Allow unbounded storage if maxSize or ttl set

v7.5.2

Compare Source

v7.5.1

Compare Source

v7.5.0

Compare Source

  • defend against mutation while iterating
  • Add rentries, rkeys, rvalues
  • remove bundler and unnecessary package.json fields

v7.4.5

Compare Source

v7.4.4

Compare Source

v7.4.3

Compare Source

v7.4.2

Compare Source

v7.4.1

Compare Source

v7.4.0

Compare Source

  • Add browser optimized webpack bundle, exposed as 'lru-cache/browser'
  • Track size of compiled bundle in CI (@​SuperOleg39)
  • Add noUpdateTTL option for set()

v7.3.3

Compare Source

v7.3.2

Compare Source

v7.3.1

Compare Source

v7.3.0

Compare Source

  • Add disposeAfter()
  • set() returns the cache object
  • delete() returns boolean indicating whether anything was deleted

v7.2.3

Compare Source

v7.2.2

Compare Source

v7.2.1

Compare Source

v7.2.0

Compare Source

  • Add reason to dispose() calls.

v7.1.3

Compare Source

v7.1.2

Compare Source

v7.1.1

Compare Source

v7.1.0

Compare Source

  • Add ttlResolution option
  • Add ttlAutopurge option

v7.0.4

Compare Source

v7.0.3

Compare Source

v7.0.2

Compare Source

v7.0.1

Compare Source

v7.0.0

Compare Source


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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR label Apr 10, 2023
@kfcampbell
Copy link
Member

If I recall correctly this is blocked by our impending ESM update.

@renovate renovate bot force-pushed the renovate/lru-cache-9.x branch 2 times, most recently from ff2cf23 to 3ae4259 Compare May 8, 2023 19:27
@renovate renovate bot force-pushed the renovate/lru-cache-9.x branch from 3ae4259 to 68e09cb Compare May 8, 2023 23:55
@gr2m
Copy link
Contributor

gr2m commented May 12, 2023

If I recall correctly this is blocked by our impending ESM update.

No this one is not a native ES Module yet. Looks like type changes that need to be addressed

@wolfy1339
Copy link
Member

Also see #349
We had some trouble updating due to some type issues

@renovate
Copy link
Contributor Author

renovate bot commented May 13, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@gr2m
Copy link
Contributor

gr2m commented May 13, 2023

I fixed the type issues, but a test is failing. Not sure where the problem lies. I think the problem is with the way we fake timers and the way TTL is calculated within the latest lru-cache

In a way the failing test "request installation again after timeout" is testing lru-cache internals, I don't think we need it, we have to trust that it's doing what it's advertising that it's doing.

I'd vote we remove the test.

@kfcampbell
Copy link
Member

I'm 👍 on that.

@gr2m
Copy link
Contributor

gr2m commented May 16, 2023

This is ready for review and merge

@gr2m gr2m merged commit eea39fd into main May 17, 2023
@gr2m gr2m deleted the renovate/lru-cache-9.x branch May 17, 2023 04:45
@github-actions
Copy link
Contributor

🎉 This PR is included in version 4.0.12 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released Type: Maintenance Any dependency, housekeeping, and clean up Issue or PR
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants