Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The question about extension upload #16

Closed
JoNoteJoMaMa opened this issue Jul 4, 2023 · 2 comments
Closed

The question about extension upload #16

JoNoteJoMaMa opened this issue Jul 4, 2023 · 2 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@JoNoteJoMaMa
Copy link

Hello, First of all, I've to say that your project is very significant.
I've forked your project and changed MrBeast images to be someone popular in my country. The question is, can I upload my version of this project to Google extension with all of your credit for this project?

@MagicJinn
Copy link
Owner

MagicJinn commented Jul 4, 2023

Hey there! I'll guide you through the process as far as I remember it. Also, if you haven't done so already, make sure that your fork is up to date with the main branch. We fixed a bunch of bugs and I created a system that indexes the images folder instead of requiring a hardcoded list in manifest.json and mrbeasify.js.

  1. Prepare the manifests: Be sure to rename the extension and give it a proper version number in the manifest.json and manifest v3.json files.
  2. Pack extensions: Create a .zip containing icons, images, manifest.json and mrbeasify.js. This is your Firefox add-on. Then create a .zip with the same contents, but instead of using the original manifest.json, rename the V3 version to manifest.json and pack that instead of the original. This is your Chrome extension.
  3. Upload your extension to the Firefox store: Go to the Firefox developer hub, click submit new add-on, then upload the .zip meant for Firefox. Make sure to fill out any information that is relevant, like required permissions etc. Publish your extension. This process can take hours to a day.
  4. Upload your extension to the Chrome store: Go to the Chrome add-on store, click the gear in the top right, click Developer Dashboard. From there I don't know the exact instructions. Beware that Google requires a 5 dollar payment from a credit card in order to upload extensions. Upload the .zip meant for Chrome, make sure to fill out any information that is relevant, like required permissions etc. Publish your extension. This process can take several days.

This should be all if I remember correctly. Uploading to the Edge store is an option, but their review process takes up to a week, and Edge users can download from the Chrome store anyway. Let me know if you have any other questions! I'm here to help!

And as for credit, you can link my Firefox extension on the Firefox add-on page, and my Chrome extension on the Chrome add-on page, or you could link my Github on both.

@MagicJinn MagicJinn added the documentation Improvements or additions to documentation label Jul 4, 2023
@MagicJinn MagicJinn self-assigned this Jul 4, 2023
@JoNoteJoMaMa
Copy link
Author

Wow, you're such a kind person. Thank you so much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants