• action: default_popup

    • select which file will serve as main UI
  • content_scripts

    • contentscript.js
    • files that run in context of the webpages we’re on
    • use this to manipulate the DOM of our webpage that our extension is looking at
    • Ctrl + Shift + I to see console logs!!
  • service_worker

    • background.js
    • JS file that runs separately from the main browser thread
    • no access to content of a webpage (no DOM access), but has capabilities to speak to your extension using the extensions messaging system
    • chrome://extensions → Click “Inspect” under Service Worker
  • chrome.scripting.executeScript

    • can use this in background.js
    • useful if u want to inject a script on demand (not automatically), when u want to execute code in response to specific events / based on conditions etc