How sorenkrabbe/chrome-salesforce-inspector works
Project type and purpose
• This is a cross-browser (Chrome & Firefox) developer extension for Salesforce.
• Its goal is to inject a metadata-rich UI layer on top of standard Salesforce pages, enabling record-level data inspection, editing, imports/exports, and limit-monitoring without leaving the Salesforce session.
File structure
Top-level:
• .circleci/, .travis.yml – CI configurations for automated builds & tests
• scripts/ – build & release scripts (chrome-dev, firefox-dev, publish)
• addon/ – the entire extension source (manifest template, HTML/CSS/JS assets, tests)
• test/org/ – metadata fixtures for running integration tests against a Salesforce org
• package.json & package-lock.json – Node build dependencies & scripts
addon/ breaks down into:
• manifest-template.json – base extension manifest (permissions, entry points)
• background.js – background/service worker logic (message routing, initialization)
• content scripts (e.g., inspect.js, data-export.js, data-import.js, limits.js) injected into Salesforce pages
• UI assets (popup.html/css/js, explore-api.html/css/js, metadata-retrieve.html/css/js, etc.)
• React/React-DOM bundles – for any React-based UI
• test-framework.html/js & individual test-*.js – in-browser unit test harness
Key insights from README
• The extension piggybacks on the user’s existing Salesforce session (re-uses cookies/session tokens).
• All Salesforce API calls go directly from the browser to Salesforce servers—no third-party backend.
• CI runs ESLint, unit tests inside a real org (via the metadata in test/org), and packages artifacts for manual release.
• Build targets: “chrome-dev-build”, “firefox-dev-build”, plus release processes that zip and upload to the stores.