DEV Community

Discussion on: Reloading your Chrome extensions on-save in VS Code!

Collapse
solomon profile image
Solomon Author

Hello @kinghat !

I just wanted to let you know that I tested the answer you linked by installing this extension, pulling this Gulpfile into my unpacked extension's directory, running gulp chrome-watch, and making trivial edits to some metadata and JavaScript. As a result, the task detected the changes:

[14:32:10] Starting 'chrome-watch'...
change detected manifest.json
change detected background.js
change detected background.js

However, when I got back to Chrome the updates hadn't been made, and I had to manually press the reload button anyway to get them to show up.

I think this is because Chrome doesn't reload extensions when the chrome://extensions page is reloaded by the "Chrome Unpacked Extension Auto Reload" tool, however that probably used to be the case.

Collapse
kinghat profile image
kinghat • Edited on

so im not using it that way. just using it to reload the extension when i save. or in the extensions case, files are changed. and it seems to be working fine.

there is this guy who was trying to fix it up but the extension author stopped replying. he has his own crx thats not been published. here is a history of the PR he was trying to make: github.com/robin-drexler/chrome-ex... you can follow his name to his GH and see his crx. though, im not using that one.

if you give that one a go, will you lmk if that one works better?

Thread Thread
solomon profile image
Solomon Author