chore(deps): bump lru-cache from 6.0.0 to 7.4.0

[dependabot]

Bumps lru-cache from 6.0.0 to 7.4.0.

Changelog

Sourced from lru-cache's changelog.

7.4.0

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

7.3.0

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

7.2.0

• Add reason to dispose() calls.

7.1.0

• Add ttlResolution option
• Add ttlAutopurge option

v7 - 2022-02

This library changed to a different algorithm and internal data structure in version 7, yielding significantly better performance, albeit with some subtle changes as a result.

If you were relying on the internals of LRUCache in version 6 or before, it probably will not work in version 7 and above.

Specific API Changes

For the most part, the feature set has been maintained as much as possible.

However, some other cleanup and refactoring changes were made in v7 as well.

• The set(), get(), and has() functions take options objects instead of positional booleans/integers for optional parameters.
• size can be set explicitly on set().
• cache.length was renamed to the more fitting cache.size.
• Deprecations:
  • stale option -> allowStale
  • maxAge option -> ttl
  • length option -> sizeCalculation
  • length property -> size
  • prune() method -> purgeStale()
  • reset() method -> clear()
• The objects used by cache.load() and cache.dump() are incompatible with previous versions.

... (truncated)

Commits

• d511442 7.4.0
• ec1dab4 changelog for 7.4.0
• d062316 ignore bundle
• 9d5bd43 compile bundle with exports, expose as lru-cache/browser
• 76b058f document noUpdateTTL
• ddc6344 Add noUpdateTTL option to set without updating TTL
• 9c05bcd ci: skip failing windows/npm version combinations
• 6a91bec ci: add size-limit integration
• e8d8f1e ci: always use latest npm
• c0f4766 add webpack integration to ship browser version
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[radomird]

@dependabot rebase

[simoneb]

@radomird I assigned you since I see you already looked into this. no urgency though

[radomird]

@simoneb I've created a ticket and added it to the Bench Board

[radomird]

Do you think it would be a good idea to update the ci workflow to use https://github.com/pkgjs/action in this repo?

[simoneb]

let's wait to roll it out in fast-jwt first, to see how it plays out. No need to create a ticket though, we can add broken PRs to the board directly as I did here.

[radomird]

@dependabot close