You should now see your BEX mounted in Chrome. Navigate to and select your `src-bex` folder.ģ. This will present you with the *folder* selection dialog. In Chrome, navigate to `chrome://extensions`Ģ. In line with the screenshot above, the following steps must be taken:ġ. Now that we've created a development environment, we need to load generated browser extension into your browser.
You will also have a set of files under `src-bex/Normally, these files are kept in memory, which is why you wouldn't see them when creating an SPA, but for Browser Extension development, physical files are required in order for the process to work.ĭo not edit anything under the `src-bex/::: You may or may not have already had a `src-bex` folder, but you will definitely have one now. Start developing a Browser Extension with just one command. Below, we'll explain the two processes in detail. With the (/start/quasar-cli), it is incredibly easy to develop and build Browser Extension distributables. Desc: The Quasar CLI list of commands when developing or building a Browser Extension (BEX).
