TL;DR: This is blog post is on how I ended up writing a GitHub template for creating browser extensions, with experience from other browser extension I've worked on, you can find it at https://github.com/notlmn/browser-extension-template/
I started working on open-source software sometime around 2016, watching Supercharged (RIP) on YouTube and making little tweaks on their repository, and also making a copy of my own. Man, those fun times.
And sometime around 2017, I found the now-famous browser extension Refined GitHub by Sindre Sorhus, which by then was in it's initial stages, and I immediately fell in love with it 😍. So, I started contributing to it, suggesting changes, implementing features suggested by other users, editing documentation, or simply triaging issues. I mean that's how one gets into open-source, even small changes like styling documentation could go a long way.
Later in 2018 I found out that Notifier for GitHub (NfG), another browser extension by Sindre, is looking for maintainers. My prior experience on Refined GitHub (RGH) helped me become a maintainer on that project, which even though is not as active as Refined GitHub, has seen a lot of changes and features added over the years.
And again, my contributions to these extensions led me to an invitation to become a collaborator on RGH. Even though my involvement on RGH has been a little hands-off, I was still contributing to it. And I really wanted NfG to be a lot more like RGH, in terms of directory structure, dependencies, and automatic deployments to extension stores so that we have a structured setup for easily managing them. At this point, most of this was achieved by simple copy-pasting code between them, as they had many shared parts.
At the same point GitHub released a new feature called template repositories, which if you do not yet know is similar to forking a repository but the source and fork are loosely related and removes most of the other annoyances like allowing the clone to be made private.
Anyway, with many people starting to create browser extensions and being made open-source, I really wanted something similar to HTML5 Boilerplate but for creating browser extensions. Even though what I wanted to create was a entirely different, the new GitHub template feature helped spark the idea.
And that's how I ended up creating browser-extension-template. The extension borrows a lot of best-practices, with tools and technologies required for building browser extensions including the following features.
- Included polyfill for cross-browser compatibility.
- Auto-syncing setup for syncing user options provided by browsers.
- Auto-publishing to extension stores using CRON jobs and weekly tagged releases.
- Extensive documentation on how to configure it (Webpack, css extraction, and even setting up Typescript).
The project also includes a sample browser extension that makes use of all of the features mentioned above.
“This extension template is heavily inspired by
hide-files-on-githubbrowser extensions. You can always refer to these browser extensions' source code if you find anything confusing on how to create a new extension.”
As mentioned in the readme, the extension borrows a lot from other browser extensions, and some of these features have also been backported to some of these extensions.
The project is almost a year old now, released under CC-0. If you are interested in building browser extensions, learning how they work, or even contribute to one, take a look at browser-extension-template.