Open heavenkiller2018 opened 1 year ago
but firefox doesn't support manifest v3:
error msg is showed in firefox
There was an error during the temporary add-on installation.
Error details
Unsupported manifest version: 3
besides, in chrome, if the background.ts is modified , I have to delete, and then reinstall the extension to put this change into effect. It's very very tedious relative to HMR. even it's better than this if only need to be reloaded but reinstalled. Is there any solution to this?
If background.ts
is in src-bex
directory than you shouldn't have to reinstall the extension every time.
There should be a reload button (docs).
now the situation is that I have to reload the extension if I have changed files in src, and reinstall if in src-bex. The anticipated behavior should be that clicking refresh(F5) is only needed if files in src is changed, and only reloading if files in src-bex.
the following is an example:
I writed a mark code in background.ts
console.count('background.ts:outer bexBackground🎯');
export default bexBackground(() => {
...
}
after install the extension
then, I changed the mark code to:
console.count('background.ts:outer bexBackground1`🎯');
then, I only reloaded the extension (of course, after the recompilation is completed).
it has proved that the change didn't work, still output the before code
the new code taked no effect until the extension was reinstalled:
so, now when I'm developing an bex with quasar, I have to reinstall the developed extension again and again. so tediously! It's aweful!
why? who can explain it?
What happened?
when I have created an browser extension project with Quasar BEX Mode, I have to reload the builded extension files everytime I made some modification to the app, this work is very tiring and tedious!also inefficient!
What did you expect to happen?
HMR just like a general Vue app, the result should be rendered immediately once the modification is finished. I have found an excellent starter template which can do it.
perhaps you could study how it realize such HMR and migrate it to Quasar, because withou HMR, it's very hard to develop an BEX application!
Reproduction URL
https://stackblitz.com/edit/quasarframework-vfcnwa
How to reproduce?
[[What is a Browser Extension | Quasar Framework](https://quasar.dev/quasar-cli-vite/developing-browser-extensions/introduction)](https://quasar.dev/quasar-cli-vite/developing-browser-extensions/introduction)
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
BEX Mode
Platforms/Browsers
Chrome
Quasar info output