3
2 Comments

What are your biggest pain points when developing a browser extension?

I'll start with mine:

  1. Hot reload. It seems like there is no solution to this problem. Constantly hitting the refresh button or reuploading the package is truly a pain in the ass.
  2. Chrome storage logging. It's not a big deal to show console.logs of your chrome storage data and observe the changes, but it would be cool to have a UI interface like the built-in LocalStorage tab in the chrome dev tools.
posted to Icon for group Browser Extension Makers
Browser Extension Makers
on September 11, 2022
  1. 4

    Solution for your pain points, which I use daily:

    1. Try to use the hotkey for reloading using the extension: https://chrome.google.com/webstore/detail/extensions-reloader/fimgfedafeadlieiabdeeaodndnlbhid
    2. Try to use the extension:
      https://chrome.google.com/webstore/detail/storage-area-explorer/ocfjjjjhkpapocigimmppepjgfdecjkb
      It is like built-in LocalStorage, but for chrome storage data. So useful.

    Hope it helps!

    1. 1

      Wow, thank you, didn't expect someone to help me with all the pain points at once :)

Trending on Indie Hackers
I'm a lawyer who launched an AI contract tool on Product Hunt today — here's what building it as a non-technical founder actually felt like User Avatar 142 comments “This contract looked normal - but could cost millions” User Avatar 54 comments A simple way to keep AI automations from making bad decisions User Avatar 47 comments 👉 The most expensive contract mistakes don’t feel risky User Avatar 41 comments The indie maker's dilemma: 2 months in, 700 downloads, and I'm stuck User Avatar 40 comments Never hire an SEO Agency for your Saas Startup User Avatar 33 comments