creating a browser extension with quasar is harder than it should be

[julie777]

Currently to create a browser extension you have to create a quasar project and then add the bex parts with "-m bex". While this works, it doesn't make getting started with a browser extension easy.

A normal quasar project can be created and then immediately run with quasar dev.
It would be nice if there was a way to create a quasar bex project that also ran immediately with and example of all the parts actually there and usable. This includes a popup, a sidebar, an options page, a page for the extension and some simple communication. It is much easier to remove what isn't needed than to go through all the steps in the doc and try to get something that works.

One example of the unnecessary difficulty is that after creating a bex, then using quasar new page PopupPage I have to go and add it to the router and the manifest.json. Then I just go and add some text to the page and run the bex. The popup opens but doesn't display correctly because the generated page file has been generated to only work with a layout.

For someone new to creating browser extensions, and new to trying to use Quasar to do it this seems complicated and frustrating.

It would also be nice if the bex supported running with firefox web-ext run which starts the browser with a temporary profile and loads the extension.

I love Quasar and don't want to use Vue directly, but it often seems to be overly complicated at times to just do something simple.

Any thoughts?

[julie777]

I forgot to mention that it seems like bex mode is still primarily focused on creating a quasar app with support for a background script. Most browser extensions are not apps, but just extensions of the browser's functionality.

It seems like a bex template for quasar that isn't a Quasar app with bex added would be more useful, more concise, and much easier to start with.