docs: Add Firefox Add-on support to homepage showcase by shadoath · Pull Request #2208 · wxt-dev/wxt

shadoath · 2026-03-23T17:19:52Z

Summary

Add optional firefoxSlug to extension entries (Chrome-only, Firefox-only, or both)
Fetch Chrome and Firefox data in a single GraphQL request using the unified Extension type
Combine user counts into one number per card, with store links (Chrome, Firefox) in the footer

Screenshot

Allow extension entries to include a firefoxSlug alongside the Chrome ID, rendering a "Firefox" badge that links to addons.mozilla.org. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

netlify · 2026-03-23T17:19:59Z

✅ Deploy Preview for creative-fairy-df92c4 ready!

Name	Link
🔨 Latest commit	`a87ef07`
🔍 Latest deploy log	https://app.netlify.com/projects/creative-fairy-df92c4/deploys/69dc6eddb208e50008208eaf
😎 Deploy Preview	https://deploy-preview-2208--creative-fairy-df92c4.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

InvictusNavarchus · 2026-03-26T05:32:30Z

I support the idea, since I also publish on Firefox Addons, but having Firefox URL optional while Chrome Extension URL required is still biased toward Chrome Extensions. What if you only publish the extension(s) on Firefox? You can't showcase it, then.

Due to smaller user base of Firefox, it actually serves as a great real testing ground with real users before finally deploying it to Chrome. So some people, including me, may publish it there first.

shadoath · 2026-03-26T12:35:51Z

I'll make that update. Also going to scrap the extensions that are already there and add the firefox slug if I can find it.

shadoath · 2026-03-26T12:52:11Z

Only used "K" and not "m" to give the number some weight, when it was 2,000k, it seemed more impressive than 2m. Also, this change helped the stats sit on a single line, making the display cleaner.

shadoath · 2026-04-09T12:35:15Z

@aklinker1 what do you think about firefox addition?

aklinker1 · 2026-04-11T16:19:31Z

Reviewing this soon! Firefox is my daily driver, so I'm down to add this for sure.

InvictusNavarchus · 2026-04-11T16:41:06Z

Only used "K" and not "m" to give the number some weight, when it was 2,000k, it seemed more impressive than 2m. Also, this change helped the stats sit on a single line, making the display cleaner.

Using the same logic, we can push it further by not doing any unit conversion at all, and let the raw count speak for itself (e.g., 200.000 users). This is currently the case for both Firefox Addons and Chrome Web Store. I'd suggest keeping it that way.

Also, this is an entirely a separate change unrelated to the main topic of this PR. I think it's better to propose this in a different PR

aklinker1 · 2026-04-11T17:27:33Z

If we want to shorten the numbers, we should use num.toLocaleString(undefined, { notation: "compact"}) and follow the locale's display preference. For me, that's 1234567 → 1.2M. I'm good with that or the full number. If we have room, I'd probably prefer the full number.

Maybe we combine the firefox and chrome stats into a single number and just add links to each of the stores? That would simplify the UI a bit and give us more room to show the full number.

Edit: Chrome reports a weekly user count vs Firefox's daily user count. The current PR ignores that, which is fine. It would also be fine to ignore the units when adding the two numbers together.

aklinker1

If you merge with main, the failing checks will pass and your PR will be deployed to preview.

Only real concern is around simplifying the data fetching by combining the firefox and chrome requests into a single graphql call. Then the whole UI could be simplified by combining the results into a single list of standardized objects before rendering them.

We should probably also add support for Edge, but I need to add that to the graphql API first as well. But ideally, this PR adds support for any number of extension stores in a generic way.

Combine Chrome and Firefox data fetching into one GraphQL request using the unified Extension type from queue.wxt.dev (v0.4.4). This addresses PR review feedback: - Delete useFirefoxAddonDetails.ts (separate Mozilla REST API calls) - Update useListExtensionDetails.ts to query both chromeExtensions and firefoxAddons via a shared ExtensionData fragment - Combine user counts into a single number per extension card - Remove link from extension name; store links (Chrome, Firefox) now appear only in the footer row - Use full locale-formatted numbers instead of custom K notation - Generic stores array supports future store additions (e.g. Edge) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

…missions

- Re-add link on extension name (defaults to Chrome, falls back to Firefox) - Fix Firefox data lookup by extracting slug from storeUrl since the GraphQL API returns numeric IDs, not slugs Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

shadoath · 2026-04-12T12:41:55Z

@InvictusNavarchus & @aklinker1. I took your comments into consideration and pushed up the simplified new version.

Let me know what you both think.

- Remove unused chromeToFirefox map - Inline sort score instead of sortKey + strip pattern Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

shadoath · 2026-04-12T12:57:38Z

@aklinker1 can we add the Firefox slug field to the Extension type query?

codecov · 2026-04-12T13:10:45Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.54%. Comparing base (99fc685) to head (a87ef07).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2208      +/-   ##
==========================================
+ Coverage   79.35%   79.54%   +0.18%     
==========================================
  Files         130      130              
  Lines        3798     3798              
  Branches      854      854              
==========================================
+ Hits         3014     3021       +7     
+ Misses        699      693       -6     
+ Partials       85       84       -1

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

pkg-pr-new · 2026-04-12T13:11:16Z

Open in StackBlitz

@wxt-dev/analytics

npm i https://pkg.pr.new/@wxt-dev/analytics@2208

@wxt-dev/auto-icons

npm i https://pkg.pr.new/@wxt-dev/auto-icons@2208

@wxt-dev/browser

npm i https://pkg.pr.new/@wxt-dev/browser@2208

@wxt-dev/i18n

npm i https://pkg.pr.new/@wxt-dev/i18n@2208

@wxt-dev/is-background

npm i https://pkg.pr.new/@wxt-dev/is-background@2208

@wxt-dev/module-react

npm i https://pkg.pr.new/@wxt-dev/module-react@2208

@wxt-dev/module-solid

npm i https://pkg.pr.new/@wxt-dev/module-solid@2208

@wxt-dev/module-svelte

npm i https://pkg.pr.new/@wxt-dev/module-svelte@2208

@wxt-dev/module-vue

npm i https://pkg.pr.new/@wxt-dev/module-vue@2208

@wxt-dev/runner

npm i https://pkg.pr.new/@wxt-dev/runner@2208

@wxt-dev/storage

npm i https://pkg.pr.new/@wxt-dev/storage@2208

@wxt-dev/unocss

npm i https://pkg.pr.new/@wxt-dev/unocss@2208

@wxt-dev/webextension-polyfill

npm i https://pkg.pr.new/@wxt-dev/webextension-polyfill@2208

wxt

npm i https://pkg.pr.new/wxt@2208

commit: a87ef07

aklinker1 · 2026-04-12T13:14:54Z

Nice, much simpler, looks great too!

@aklinker1 can we add the Firefox slug field to the Extension type query?

Sure, I can add that!

aklinker1 · 2026-04-12T13:15:38Z

Is this what you wanted? wxt-dev/queue@3ce60f3#diff-70f27b1705e6c4424067f93d1d897f8f48711869f34688493bf0d16b1e8d0f1e

It's deployed

shadoath · 2026-04-12T16:59:00Z

The slug option will clean up some logic here. If that is done first. But we don’t need to wait that change can be another PR.

…

On Sun, Apr 12, 2026 at 09:16 Aaron ***@***.***> wrote: *aklinker1* left a comment (wxt-dev/wxt#2208) <#2208 (comment)> Do you want to use in this PR for something, or can I merge? — Reply to this email directly, view it on GitHub <#2208 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAO3DJFE67XIDKAB2QBDWI34VOJJDAVCNFSM6AAAAACW4M44FSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DEMZRGU3TSNRTHA> . You are receiving this because you were assigned.Message ID: ***@***.***>

Use the new `slug` field from the GraphQL API to key Firefox results instead of parsing it from storeUrl with a regex. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

The slug field is on FirefoxAddon type only, not the shared Extension type. Move it out of the ExtensionData fragment and query it inline on firefoxAddons. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

aklinker1 · 2026-04-13T04:01:55Z

Sweet, gonna merge, then move the list to a YML file outside the vue component lol. It's gotten quite large.

aklinker1 · 2026-04-13T04:22:20Z

Having problems with github actions... one sec...

github-actions · 2026-04-13T04:24:39Z

Thanks for helping make WXT better!

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Aaron <aaronklinker1@gmail.com>

docs: Add optional Firefox Add-on links to homepage extension showcase

f1567b6

Allow extension entries to include a firefoxSlug alongside the Chrome ID, rendering a "Firefox" badge that links to addons.mozilla.org. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

shadoath requested a review from aklinker1 as a code owner March 23, 2026 17:19

github-actions bot assigned shadoath Mar 23, 2026

allow optional FF or Chrome

d27c0d7

Dynamic firefox or chrome display

a13322d

Merge branch 'main' into sb/feat/firefox-submissions

786a9b5

aklinker1 requested changes Apr 11, 2026

View reviewed changes

Comment thread docs/.vitepress/composables/useFirefoxAddonDetails.ts Outdated

Comment thread docs/.vitepress/components/UsingWxtSection.vue Outdated

shadoath and others added 3 commits April 11, 2026 23:28

Merge remote-tracking branch 'upstream/main' into sb/feat/firefox-sub…

9335f0b

…missions

shadoath changed the title ~~docs: Add optional Firefox Add-on links to homepage showcase~~ docs: Add Firefox Add-on support to homepage showcase Apr 12, 2026

shadoath requested a review from aklinker1 April 12, 2026 12:42

chore: Remove dead code and simplify sort logic

ea76d28

- Remove unused chromeToFirefox map - Inline sort score instead of sortKey + strip pattern Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

aklinker1 approved these changes Apr 12, 2026

View reviewed changes

Standardize entry format

93c58a7

aklinker1 reviewed Apr 12, 2026

View reviewed changes

Comment thread docs/.vitepress/components/UsingWxtSection.vue Outdated

shadoath and others added 5 commits April 12, 2026 15:44

Standardize entry format

3222859

Use the new `slug` field from the GraphQL API to key Firefox results instead of parsing it from storeUrl with a regex. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Merge branch 'main' into sb/feat/firefox-submissions

fba8ace

fix: Query slug only on firefoxAddons, not shared fragment

7ea8624

The slug field is on FirefoxAddon type only, not the shared Extension type. Move it out of the ExtensionData fragment and query it inline on firefoxAddons. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Map firefox slug to ID for consistency

6d88386

Merge branch 'main' into sb/feat/firefox-submissions

d7e61b1

aklinker1 enabled auto-merge (squash) April 13, 2026 04:02

aklinker1 added 2 commits April 12, 2026 23:11

Merge branch 'main' into sb/feat/firefox-submissions

fa99a60

Merge branch 'main' into sb/feat/firefox-submissions

a87ef07

aklinker1 merged commit 3205802 into wxt-dev:main Apr 13, 2026
18 checks passed

aklinker1 mentioned this pull request Apr 13, 2026

docs: Move homepage extensions to separate YAML file #2255

Merged

PatrykKuniczak mentioned this pull request Apr 13, 2026

docs: Add TF2 Trader to the list of extensions #2213

Merged

aklinker1 added a commit that referenced this pull request Apr 13, 2026

docs: Add Firefox Add-on support to homepage showcase (#2208)

9cd66ce

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Aaron <aaronklinker1@gmail.com>

Uh oh!

Conversation

shadoath commented Mar 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Screenshot

Uh oh!

netlify bot commented Mar 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Deploy Preview for creative-fairy-df92c4 ready!

Uh oh!

InvictusNavarchus commented Mar 26, 2026

Uh oh!

shadoath commented Mar 26, 2026

Uh oh!

shadoath commented Mar 26, 2026

Uh oh!

shadoath commented Apr 9, 2026

Uh oh!

aklinker1 commented Apr 11, 2026

Uh oh!

InvictusNavarchus commented Apr 11, 2026

Uh oh!

aklinker1 commented Apr 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

aklinker1 left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

shadoath commented Apr 12, 2026

Uh oh!

shadoath commented Apr 12, 2026

Uh oh!

codecov bot commented Apr 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

pkg-pr-new bot commented Apr 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

aklinker1 commented Apr 12, 2026

Uh oh!

aklinker1 commented Apr 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

shadoath commented Apr 12, 2026 via email

Uh oh!

Uh oh!

aklinker1 commented Apr 13, 2026

Uh oh!

aklinker1 commented Apr 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Apr 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

shadoath commented Mar 23, 2026 •

edited

Loading

netlify bot commented Mar 23, 2026 •

edited

Loading

aklinker1 commented Apr 11, 2026 •

edited

Loading

aklinker1 left a comment •

edited

Loading

codecov bot commented Apr 12, 2026 •

edited

Loading

pkg-pr-new bot commented Apr 12, 2026 •

edited

Loading

aklinker1 commented Apr 12, 2026 •

edited

Loading

aklinker1 commented Apr 13, 2026 •

edited

Loading