@extension-report/doctor

CLI diagnostics for @extension-report/js integrations.

Usage

npx @extension-report/[email protected] --public-key pk_er_... --manifest manifest.json

Run the doctor against the built manifest before every extension store submission. Store builds should pin exact SDK package versions, for example "@extension-report/js": "0.6.2" instead of using a caret range, and keep every @extension-report/* SDK package on the same version. The store-validation runbook is in the repository docs: https://github.com/Amorem/extension.report/blob/main/docs/sdk-store-validation.md.

By default the doctor:

• reads the extension manifest;
• checks the required storage, alarms, effective host permission, and background entrypoint;
• detects the installed SDK version;
• requests /api/v2/config?pk=... to verify the public key, collection kill-switch, and min_sdk_version compatibility;
• posts a diagnostic batch to /api/v2/events?dry_run=1, which validates the payload without ingesting events.

Options:

extension-report-doctor --public-key pk_er_...
extension-report-doctor --manifest .output/chrome-mv3/manifest.json
extension-report-doctor --api-base-url https://extension.report/api
extension-report-doctor --json