Menu

Post image 1
Post image 2
1 / 2
0

From Zero to AMO: How to Publish a Firefox Extension Without Losing Your Mind

DEV Community·Weather Clock Dash·29 days ago
#DU0HUNcg
Reading 0:00
15s threshold

Publishing to Mozilla's Add-ons site (AMO) is different from any other app store. Here's exactly what I learned going through the process with Weather & Clock Dashboard. The Manifest Version Situation Firefox currently supports both Manifest V2 and V3. Chrome is forcing V3 (which has significant limitations for ad blockers). Firefox's stance is more pragmatic — they support both and have promised to maintain V2 support longer. For a new extension in 2024, use MV3. Here's the basic manifest.json : { "manifest_version" : 3 , "name" : "Your Extension" , "version" : "1.0" , "permissions" : [ "storage" ], "browser_specific_settings" : { "gecko" : { "id" : "yourextension@yourdomain.com" } } } Enter fullscreen mode Exit fullscreen mode The browser_specific_settings.gecko.id is required for AMO and optional for Chrome. Include it.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More