RARaed667·Jul 5, 2022
This is pretty cool, bundle it with webextension-polyfill [0] and you can release it as a decent NPM package.
[0] https://github.com/mozilla/webextension-polyfill
In Show HN: Typed React useStorage hook for Chrome extensionsmozilla
webextension-polyfill
JavaScript2017–2025
mozilla / webextension-polyfill · Archived
webextension-polyfill
A lightweight polyfill library for Promise-based WebExtension APIs in Chrome
18Distinct people
22Mentions
0Explicit recommenders
3.1KGitHub stars
What to know before exploring
What it is
A lightweight polyfill library for Promise-based WebExtension APIs in Chrome
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 10:56:20 AM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year22 dated mentions
Observed mentions: 2017-08-01 19:24:06 UTC to 2025-06-22 14:02:41 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
4 sourcesThere's standardization work being done at the moment with the W3C WebExtensions Community Group [1] which is definitely a step in the right direction!
Mozilla has also done some great work building a web extension polyfill library that attempts to abstract away the differences between the browsers [2] but the translation will always be imperfect, and edge cases are abundant.
[1]: https://www.w3.org/community/webextensions/
[2]: https://github.com/mozilla/webextension-polyfill
In Show HN: Plasmo – a framework for building modern Chrome extensionsI've written extensions before and Firefox has a very good polyfill [0] that makes it quite easy to write extensions for all browsers. It does get a bit trickier if you also want to incorporate TypeScript [1] or React however.
[0] https://github.com/mozilla/webextension-polyfill
[1] https://github.com/Lusito/webextension-polyfill-ts
In It’s Like GPT-3 but for Code – Fun, Fast, and Full of FlawsI used WebExtension polyfill[0] when adapting my FF addon to Chrome and admittedly all the intricate differences between APIs still costed me half a day of work.
I managed to have it done with only a few places where I branch on navigator.vendor, but If I wanted to ship different versions to AMO and CWS, I'd make use of something like DefinePlugin[1] for webpack to include/exclude code based on build target.
[0] https://github.com/mozilla/webextension-polyfill/
[1] https://github.com/webpack/docs/wiki/list-of-plugins#definep...
In Ask HN: Browser-extension creators, how do you write for multiple browsers?