Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Reload the extension as well as the pages #174
If you let it reload every time livereload is triggered by the watch and a bunch of files were updated at once, livereload sends a bunch of messages in a row - 1 for each updated file. Chromereload.js catches each of those messages and reloads the extension multiple times in a row. When that happens Chrome catches the fact that the extension is constantly reloading and disables the extension.
1 minute was an arbitrary setting but so far it's worked for me. Chrome is no longer disabling my extension and I don't usually make changes faster than 1 minute.
I really think that the gulp task really needs modified so that it waits for all the files to be finished updating and only calls livereload.reload once after all the triggers for all the files that were updated.