Publishing a Chrome browser extension

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
Search for a command to run...

I'm a full-stack developer from South Africa 🇿🇦. I love writing about JavaScript, HTML and CSS.
No comments yet. Be the first to comment.
Today's article will look at creating a Chrome dev tools extension. It will be a basic setup. For now, that doesn't do anything yet. It just shows you how we can inject something into the dev tools. The result will look like this: Creating a Chrome ...
Most of you know me for my consistency, a golden arrow in my blog series. I've written 1000 articles in 1008 days! Almost an article a day, and my honeymoon was the only holiday I ever took. I'm super proud of this achievement; it has been a fantasti...

It's not the first time I'll be talking about community. I think it's an essential aspect of any successful tool. This shows in my previous explorations of Astro, Medusa, and now Vendure as well. All these products thrive in a super open, welcoming, ...

The cool part about Vendure is how easy it is to set up and how abstract each layer is. Basically, we get the following elements: External database Server Worker Admin UI Frontend While this is amazing, it also brings a bit of complexity when it co...

The previous article looked at customizing Vendure on a data and process level. In this article, we'll look at customizing emails, as they are often a big part of a webshop system. We'll be looking at two different layers of customization for customi...

Even though Vendure is a pretty significant project out of the box, in some cases, we might want to go in and modify some elements to work to our specific use case. In this article, I'll take a high-level look at some elements we can customize within...

Now that we created the TurboReader browser extension, I wanted to see what's involved in actually getting it in the stores.
I decided to only ship it to the Chrome store for now. In future articles, I might go into the other stores as well.
The first step is to navigate to the Chrome web store developer portal. This is where you'll manage your extensions.
Visit the Chrome Web Store portal
If you don't have an account, you'll be asked to create one here. You'll need to pay the 5$ (one-time) registration fee.

Once logged in and registered for the portal, you'll be asked to complete your profile. This could entail several questions. The portal gives excellent feedback on what you might be missing.
After that, you'll be able to add a new item. Click on the items tab in the left sidebar and click on a new item.

You'll see a popup where you need to submit a zip file of your project. Go ahead and zip your whole extension directory. The portal will now verify your zip and ensure the manifest is alright.
Once done, you'll enter the detail item view, and you'll have to fill out some required fields:
Then on the Privacy tab, you'll have another set of required fields:
If unsure which field you might be missing, click on the "Why can't I submit" link at the top. This will tell you what's missing.

Once you have all fields, click the "Submit for review" button on the top.
It will notify you that the submission is on its way.
Do note it can take quite some time, especially if this is your first submission. The Chrome team might also reject your app, listen carefully to their response and adjust accordingly.
And that's it. You now have your first extension in the Chrome store.
Checkout TurboReader in the Chrome store.
Thank you for reading my blog. Feel free to subscribe to my email newsletter and connect on Facebook or Twitter