Skip to content

Ask HN: What WebExtension problem would you like to be solved?

3 pointsfregante2 comments
On HN

I’ve been working on browser extensions for a few years and along the way I tried to solve problems that the chrome.* APIs made difficult to achieve or that are simply common. One such example is enabling content scripts on new origins without having to specify them in the manifest.json[1], with just 2 lines of code (via 2 modules) and no UI.

What other little and big problems do you encounter when developing extensions?

[1] https://github.com/fregante/webext-dynamic-content-scripts/blob/master/how-to-add-github-enterprise-support-to-web-extensions.md

Comments

How do you handle cache in your extensions? There's no way to store information temporarily except with sessionStorage and cookies.

I wrote some code specifically for this, actually. It still uses the regular chrome storage API, but they expire after a while:

https://github.com/fregante/webext-storage-cache

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.