webextension-polyfill

A lightweight polyfill library for Promise-based WebExtension APIs in Chrome (by mozilla)

Webextension-polyfill Alternatives

Similar projects and alternatives to webextension-polyfill

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better webextension-polyfill alternative or higher similarity.

webextension-polyfill reviews and mentions

Posts with mentions or reviews of webextension-polyfill. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-12-19.
  • Show HN: Chrome Reaper
    4 projects | news.ycombinator.com | 19 Dec 2023
    Porting this extension to Firefox should be relatively straightforward using the webextension polyfill: https://github.com/mozilla/webextension-polyfill
  • Show HN: OpenAPI DevTools – Chrome ext. that generates an API spec as you browse
    17 projects | news.ycombinator.com | 25 Oct 2023
    Firefox maintain a library for unified extension API https://github.com/mozilla/webextension-polyfill

    Their type definition for HAR request isn't exported https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast...

  • can you convert a simple firefox addon to be used with chrome?
    1 project | /r/chrome_extensions | 31 Oct 2022
    best is to use https://github.com/mozilla/webextension-polyfill
  • Browser Extension with Blazor WASM - Cross-Browser Compatibility
    2 projects | dev.to | 5 Sep 2022
    The Browser Extension Working Group at W3.org proposes the web standards based on the Chrome extension manifest, which supports all web browsers. Based on that proposal, Mozilla has released the Browser Extension Polyfill library that supports the modern promise pattern instead of callback. Therefore, if you import this polyfill library, theoretically, your Chrome extension quickly turns into the browser extension that runs on multiple browser engines.
  • IWTL how to make simple chrome extensions.
    1 project | /r/IWantToLearn | 2 Aug 2022
    And the biggest tip that i received late. Use Typescript type by Mozilla to make your development much easier(autocomplete, inline docs etc): https://github.com/mozilla/webextension-polyfill
  • Show HN: Plasmo – a framework for building modern Chrome extensions
    8 projects | news.ycombinator.com | 3 Jun 2022
  • It’s Like GPT-3 but for Code–Fun, Fast, and Full of Flaws
    5 projects | news.ycombinator.com | 19 Mar 2022
    I'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

  • Ask HN: Browser-extension creators, how do you write for multiple browsers?
    6 projects | news.ycombinator.com | 12 Feb 2022
    I 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...

  • Creating a browser extension for Safari and Chrome
    5 projects | dev.to | 19 Jan 2022
    Initially I created wrapper functions to convert Chrome functions that require callback to return promise instead. The better approach, as I found out later, is probably to use webextension-polyfill from Mozilla and its types.
  • Firefox Addons Unable to Update, Undisclosed AMO Issues
    2 projects | news.ycombinator.com | 25 Sep 2021
    I mean, the browser apis are close (and Mozilla still has much better documentation) but there are a LOT of edges cases where behavior diverges.

    Frankly - I'm a little peeved that Optional permissions in Firefox are STILL broken - The prompt can only be triggered in response to a user action, and Firefox blows the fuck up if you put a promise anywhere in between the user click and the call to the api. Which is hugely ironic, since Mozilla is the one pushing to move all the webext APIs to be promise based (and provides a nice helpful library for Chrome/Edge/Safari support: https://github.com/mozilla/webextension-polyfill) which... doesn't work on their platform. Doubly ironic, since the result is that most FF extensions just ask for more permissions up front, which is exactly the opposite of what you'd want in the "secure/private" world Mozilla claims they're pushing towards.

  • A note from our sponsor - InfluxDB
    www.influxdata.com | 25 Apr 2024
    Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →

Stats

Basic webextension-polyfill repo stats
18
2,535
4.7
about 2 hours ago

Sponsored
Power Real-Time Data Analytics at Scale
Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
www.influxdata.com