A collection of simple, complete, and installable example Firefox add-ons built using the WebExtensions API.
webextensions-examples is a repository of example browser extensions created using the WebExtensions API. It provides complete, working examples that demonstrate how to build browser add-ons that modify browser behavior or web page content. These examples serve as practical learning resources and starting points for developers creating their own extensions.
Developers learning to build browser extensions, particularly those targeting Firefox or cross-browser compatibility using the WebExtensions standard.
It offers real, working code examples maintained by Mozilla's Add-ons team, providing authoritative demonstrations of WebExtensions API usage that can be immediately tested and adapted for new projects.
Example Firefox add-ons created using the WebExtensions API
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Built on standard WebExtensions APIs, ensuring compatibility with Firefox, Chrome, Opera, and Edge, as emphasized in the README's focus on cross-browser support.
Each example is a complete, installable extension that can be loaded directly into Firefox via about:debugging or web-ext, providing practical, real-world code demonstrations.
Maintained by Mozilla's Add-ons team, the examples reflect best practices and up-to-date API usage from official MDN documentation.
Supported by a discourse forum and issue tracker, offering clear avenues for help and contribution, as outlined in the README's 'Problems?' section.
Examples are primarily tested in Firefox, and using them in Chrome requires Mozilla's polyfill, adding setup complexity and potential compatibility hiccups.
Focused on simple demonstrations, the examples may not cover complex scenarios like performance optimization or integration with modern frameworks, leaving developers to extend them.
While web-ext is recommended for features like automatic reloading, it requires separate installation and configuration, increasing initial setup overhead.