Closed shash7 closed 12 months ago
Likely dead cause of the Manifest V3
I would love to find a good alternative :/
Maybe this https://github.com/sanyu1225/vue-cli-plugin-chrome-extension-cli . Would love to hear what other people are using.
@jculverwell Is there also a Firefox version available?
Finally I got Manifest 3 working in this after 10 days of research
@sherifmayika how?
@sherifmayika how?
https://github.com/adambullmer/vue-cli-plugin-browser-extension/issues/107 followed this then did some reaserch where are you stuck at? I have everything working including firebase disabled hot reload
@jculverwell Is there also a Firefox version available?
with little tweak you can turn your product suitable for firefox
@sherifmayika
disabled hot reload
Thanks for the link, it was very helpful!
What did you do to disable hot reloading besides pulling out the webpack-extension-reloader library, and nuking the references to the reloader in index.js? Anything else?
yes, I would mostly consider this a dead project. the vue community has dramatically changed the tooling ecosystem since this started (i.e. vite), manifest v3 has added some complexities to local development, and some of the existing livereload solutions never worked that well to name a few of the challenges in maintenance for this project. Some updates have been made to help existing projects limp along
Appreciate the closure @adambullmer Build my first product(Snapfont) on this years ago.
Seems like there are heaps of bugs regarding v3 manifest(mainly csp and background service workers) which haven't been resolved and no major updates have been made in this area.
So is this project dead? And if yes, what are the alternatives?