How googlechromelabs/projectvisbug works
Project type and purpose
• This is an open-source browser extension (VisBug) plus accompanying demo/static site, with a Safari desktop extension packaged in an Xcode project.
• Purpose: Provide in-page web design/debug tooling by injecting UI elements/components into any website at runtime.
File structure
• Top level:
• .github/workflows → CI (build & test pipelines)
• VisBug/VisBug Extension & VisBug.xcodeproj → Safari extension mac app
• extension/ → Chrome/Edge/Firefox extension source & manifest
• app/ → Demo site, built docs, feature‐driven modules, utilities, components, plugins
• assets/ → static assets (images, Sketch files)
• rollup.config.mjs, package.json → bundler config & npm scripts
• firebase.json, app.yaml, .firebaserc → hosting/deploy config
• Patterns:
• Modular feature architecture (app/features, app/components, app/plugins)
• Web Components (custom elements, CSS modules)
• Bundled outputs for extension vs demo site
README for additional insights
• Core design/debug tool
• Built to “point, click & tinker” with site DOM
• Supports multiple browsers (Chrome, Firefox, Safari, Edge)
• Uses Chrome-extension manifest + browser APIs
• Demo site hosted on Firebase/GCP
Essential detail checklist
• build steps separately from runtime flow
• multi-browser packaging
• Web Component registry and dynamic injection mechanism
• CI tests and deployment to stores/hosts