Add Support for Firefox

[Rupert28]

Begun work on modifying build so it works on Firefox-based browsers.

• Firefox only supports manifest V2 unlike Chrome's V3
• Made a new template.firefox.json for creating a V2 manifest for Firefox
• Will require env variables to be passed during dev builds, e.g. npm run build:firefox
• Various other changes to make manifest supported by Firefox, for example service_workers aren't supported, so a scripts array must be passed.

Will hopefully be able to work on this further.

[janbaykara]

I would like to migrate the build rig to use the cross-browser extension framework https://crxjs.dev/guide/installation/create-crxjs at some point

I leave it to your judgement about whether it's easier to accomplish your goal via the current build step, or if that framework solves anything for you, in which case feel free to throw that into this PR maybe?

Happy either way! (CC @danitt for your thoughts on whether that's theoretically wise.)

[danitt]

I would like to migrate the build rig to use the cross-browser extension framework https://crxjs.dev/guide/installation/create-crxjs at some point

I leave it to your judgement about whether it's easier to accomplish your goal via the current build step, or if that framework solves anything for you, in which case feel free to throw that into this PR maybe?

Happy either way! (CC @danitt for your thoughts on whether that's theoretically wise.)

I'm happy to attempt porting the framework before @Rupert28 gets too far into this pr

(especially because Zen browser is slowly becoming my fav browser .. and it's built on FF engine)

[Rupert28]

A framework definitely seems like a good idea! I probably should've considered that lol.

After a quick google I found wxt.dev, which supports more browsers than CRXJS (Chrome, Firefox, Edge, Safari, Chromium-based browsers). Would that one be a better choice? That way we could port to a framework and add FF (and a bunch of other) support in one go!

Zen is also becoming my favourite browser too except for it stealing waaayyy too much RAM...

Edit: I'm happy to have a go migrating to WXT if that's the way you guys want to go. I'd probs do it in a seperate PR and close this off just for consistency

[danitt]

A framework definitely seems like a good idea! I probably should've considered that lol.

After a quick google I found wxt.dev, which supports more browsers than CRXJS (Chrome, Firefox, Edge, Safari, Chromium-based browsers). Would that one be a better choice? That way we could port to a framework and add FF (and a bunch of other) support in one go!
Edit: I'm happy to have a go migrating to WXT if that's the way you guys want to go. I'd probs do it in a seperate PR and close this off just for consistency

at a cursory glance both CRXJS and WXT look decent (solid stack, healthy contribution history, good docs), but due to the browser suppoort WXT might be a nicer way to go. I'll have a closer look later - good suggestion @Rupert28 🔥

[janbaykara]

In favour of wider distribution as long as DX remains comfortable for contributors!

[danitt]

hey all, happy to report the migration effort to wxt is mostly done and looking pretty darn good 🎉

everything lints, compiles, and statically looks more or less correct, but I've yet to do any runtime testing - anyone willing to jump and verify / fix the remaining bits would be more than welcome 🙏🏻

#71