リポジトリの原文
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Quasar Browser Extension Development
Use this skill with quasar-development for shared UI and application concerns.
Map extension contexts
- Inspect
quasar.config.* > bex,src-bex/manifest.json, background scripts, content scripts, injected scripts, popup/options pages, and bridge usage. - Read the current Quasar BEX documentation and target-browser extension documentation.
- Add the mode with
quasar mode add bex. - Identify each execution context and its available APIs before changing code.
Minimize privilege and trust
- Request only required permissions, host permissions, and web-accessible resources.
- Treat page DOM, page messages, storage, tabs, and external messages as untrusted input.
- Validate message origin, shape, channel, and response before privileged actions.
- Use the BEX bridge for supported cross-context communication; handle teardown and navigation cleanly.
- Keep privileged APIs in the background context and expose narrow operations to content/UI contexts.
- Respect Manifest V3 service-worker suspension: persist required state and do not rely on long-lived globals.
- Avoid remote code and dynamic execution that violate browser store policies or CSP.
- Account for API and manifest differences between Chrome-family browsers and Firefox.
Validate in target browsers
- Run
quasar dev -m bex -T chromeor the supported target and load the development extension. - Test installation, update, browser restart, tab navigation, service-worker restart, and permission denial/removal.
- Test every content-script match pattern against intended and unintended pages.
- Build with
quasar build -m bex -T <target>and inspect the emitted manifest and package contents. - Run tests, typecheck, lint, formatting, and store-policy checks for each supported browser.
