A barebones cross-browser extension boilerplate with Parcel 2, auto-syncing options, and auto-publishing workflows.
browser-extension-template is a minimal boilerplate for creating cross-browser extensions with modern tooling. It provides a ready-to-use setup with Parcel 2 for bundling, automated options management, and built-in workflows for publishing to extension stores. It solves the problem of repetitive configuration and manual deployment for extension developers.
Developers building browser extensions for Chrome, Firefox, or other WebExtensions-compatible browsers who want a streamlined, automated starting point.
It eliminates boilerplate setup with pre-configured Parcel 2 builds, auto-syncing options, and one-click publishing workflows, allowing developers to ship extensions faster with less maintenance overhead.
📕 Barebones boilerplate with Parcel 2, options handler and auto-publishing
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Designed for seamless compatibility with both Chrome and Firefox, using Parcel's browser-target transpilation to handle differences automatically.
Includes GitHub Actions that auto-version and publish to Chrome Web Store and Mozilla Add-ons, reducing manual deployment overhead as described in the publishing section.
Leverages Parcel 2 for zero-config bundling, allowing developers to start coding immediately without complex build setup, as highlighted in the Parcel 2 integration.
Integrates webext-options-sync to automatically save, restore, and migrate user options, simplifying state management without extra code.
Defaults to targeting only the latest browser versions, which may exclude older environments without manual Parcel configuration, as noted in the Configuration section.
Auto-publishing heavily relies on GitHub Actions and secret setup, making it cumbersome for teams using other CI/CD platforms or wanting more deployment flexibility.
As a barebones template, it lacks built-in testing frameworks, UI libraries, or advanced scaffolding, requiring additional setup for complex extensions.