Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more! Learn more →
Webextension-polyfill Alternatives
Similar projects and alternatives to webextension-polyfill
-
esbuild-react-chrome-extension
Simple chrome extension with React and Typescript, bundled by esbuild
-
browser-extension-svelte
A simple cross-browser extension made with Svelte
-
Klotho
AWS Cloud-aware infrastructure-from-code toolbox [NEW]. Build cloud backends with Infrastructure-from-Code (IfC), a revolutionary technique for generating and updating cloud infrastructure. Try IfC with AWS and Klotho now (Now open-source)
-
-
uBlock-Safari
uBlock Origin - An efficient blocker for Chromium, Firefox, and Safari. Fast and lean.
-
webext-redux
A set of utilities for building Redux applications in Web Extensions.
-
testing-playground
Simple and complete DOM testing playground that encourage good testing practices.
-
web-ext
A command line tool to help build, run, and test web extensions
-
Appwrite
Appwrite - The Open Source Firebase alternative introduces iOS support . Appwrite is an open source backend server that helps you build native iOS applications much faster with realtime APIs for authentication, databases, files storage, cloud functions and much more!
-
browser-ext-react-esbuild
Browser extension implemented in TypeScript & React and built by esbuild for Chrome, Safari and possibly Mozilla Firefox
-
google-meet-push-to-talk
Chrome extension that enables push-to-talk for Google Meet
-
uBlock
uBlock Origin - An efficient blocker for Chromium and Firefox. Fast and lean.
-
picard
PICARD - Parsing Incrementally for Constrained Auto-Regressive Decoding from Language Models. PICARD is a ServiceNow Research project that was started at Element AI. (by ServiceNow)
-
-
webextensions-examples
Example Firefox add-ons created using the WebExtensions API
-
-
Ka-Block
A Safari extension that blocks an artisanal selection of advertising domains.
-
spider
scripts and baselines for Spider: Yale complex and cross-domain semantic parsing and text-to-SQL challenge
-
CoderCalendar-Extensions
Browser extensions for competitive programming enthusiasts
-
ExtPay
The JavaScript library for ExtensionPay.com — payments for your browser extensions, no server needed.
-
sveltekit-adapter-browser-extension
Build browser extensions with Svelte (early prototype)
-
-
Sonar
Write Clean JavaScript Code. Always.. Sonar helps you commit clean code every time. With over 300 unique rules to find JavaScript bugs, code smells & vulnerabilities, Sonar finds the issues while you focus on the work.
webextension-polyfill reviews and mentions
-
Browser Extension with Blazor WASM - Cross-Browser Compatibility
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.
- Show HN: Plasmo – a framework for building modern Chrome extensions
-
It’s Like GPT-3 but for Code–Fun, Fast, and Full of Flaws
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.
-
Ask HN: Browser-extension creators, how do you write for multiple browsers?
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
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
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.
- How has your experience been building browser extensions?
- Manifest v3 Update
-
It's time to port your extension to Firefox
I would probably look into using https://github.com/mozilla/webextension-polyfill/ from the start. From my point of view the the Promise based API is much nicer to use.
Looks like there's a polyfill you can use https://github.com/mozilla/webextension-polyfill
-
A note from our sponsor - Appwrite
appwrite.io | 7 Jun 2023
Stats
mozilla/webextension-polyfill is an open source project licensed under Mozilla Public License 2.0 which is an OSI approved license.
The primary programming language of webextension-polyfill is JavaScript.
Popular Comparisons
- webextension-polyfill VS esbuild-react-chrome-extension
- webextension-polyfill VS browser-extension-svelte
- webextension-polyfill VS uBlock-Safari
- webextension-polyfill VS plasmo
- webextension-polyfill VS webext-redux
- webextension-polyfill VS testing-playground
- webextension-polyfill VS browser-ext-react-esbuild
- webextension-polyfill VS web-ext
- webextension-polyfill VS google-meet-push-to-talk
- webextension-polyfill VS template