Thanks for writing a nice and simple introduction into how to create extensions! I think a lot of people are not aware of how easy it is to create an extension, so this does a good job of showing the basics of it!
Since you’re creating a series around this topic, I would recommend you mention the importance of supporting v3 moving forward. I know that firefox currently does not support v3, but when you develop more and more extensions you’ll realize anyway that you can’t really write the same code or tutorial for both browsers. Also, moving from v2 to v3 can be difficult as there are many changes between the two versions.
According to this seems like Firefox will be supporting v3 by the end of this year. However, they’re looking into different ways for adapting it. So, again, one codebase for an extension wouldn’t be enough, you would need to write 2 to support chrominum browsers and firefox.
Honestly, after publishing two extensions, I found managing that a hassle and fully dropped support for firefox. Not sure how other devs feel about this too 😅
We still run mv2 for daily .dev and so far it's been good with one build.
However we're lucky to be a "older" extension so not forced to migrate to 3 for Chrome standards.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for writing a nice and simple introduction into how to create extensions! I think a lot of people are not aware of how easy it is to create an extension, so this does a good job of showing the basics of it!
Since you’re creating a series around this topic, I would recommend you mention the importance of supporting v3 moving forward. I know that firefox currently does not support v3, but when you develop more and more extensions you’ll realize anyway that you can’t really write the same code or tutorial for both browsers. Also, moving from v2 to v3 can be difficult as there are many changes between the two versions.
Yeah I think the new ones I use v3 all over.
I default to v2 as we need to support firefox, would really wish they hurry up and make it accept v3 😢
According to this seems like Firefox will be supporting v3 by the end of this year. However, they’re looking into different ways for adapting it. So, again, one codebase for an extension wouldn’t be enough, you would need to write 2 to support chrominum browsers and firefox.
Honestly, after publishing two extensions, I found managing that a hassle and fully dropped support for firefox. Not sure how other devs feel about this too 😅
We still run mv2 for daily .dev and so far it's been good with one build.
However we're lucky to be a "older" extension so not forced to migrate to 3 for Chrome standards.