New cache implementation

[dotconnor]

What methods should I implement besides get/set?

• set
• get
• has
• purge (clean up old/unused cached data)

Closes #2100

Test

https://github.com/sindresorhus/refined-github (Open devtools on the background page to see the console, repo pages use release-count and default-branch caches)

[fregante]

Apart from the review, is this PR still a WIP?

[dotconnor]

@bfred-it I'm good with this when you are.

[fregante]

The suggested test isn't working in Chrome nor Firefox. They appear in the cache but the cached releases number isn't picked up and shown elsewhere

👌

[dotconnor]

@bfred-it Looks like the default branch one is working (for me at least), still trying to figure out why the release count one isn't working.

[fregante]

Thanks for this! Are you interested in publishing it as a module? I’ve been wanting to publish a module like this as webext-storage-cache

[dotconnor]

@bfred-it https://github.com/dotconnor/webext-cache

[fregante]

I'd have preferred webext-storage-cache because there's also the regular browser cache which might be confused with it. If you prefer I can publish and mainain the module as my own

[fregante]

I got the repo transfer, thanks! Can you npm unpublish webext-cache --force to avoid duplicates? I just published a temporary webext-storage-cache

Storage Cache for Web Extensions
https://github.com/dotconnor/webext-storage-cache#readme

dist
.tarball: https://registry.npmjs.org/webext-storage-cache/-/webext-storage-cache-0.0.0.tgz
.shasum: ad847845ce2cb56ce53c89b68a991d46635e2c1c
.integrity: sha512-ZwBQLPHrETO5uf81Cw4iTr75KaQj5vGs8vW3LXfm1pl3FitflGMB2h/x1zEs8c5nkGJWseD6sF3dftx4XJ2ZgA==
.unpackedSize: 4.7 kB

dependencies:
webext-detect-page: ^0.9.1 

maintainers:
- bfred-it <npm@bfred.it>

dist-tags:
latest: 0.0.0  

published 2 minutes ago by bfred-it <npm@bfred.it>

[notlmn]

I'd suggest to open a new issue to track the migration process, updating across all features that use cache.

[fregante]

You can use the local version for now. When I'm ready with the npm module I'll just implement it in RGH. Only 2 features use it at the moment.