Auto-reload an unpacked extension whenever a specific file changes
Reported by
callum.l...@gmail.com,
Jul 27 2016
|
|
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36 Steps to reproduce the problem: Develop a Chrome extension, using some tooling to rebuild it automatically while you work. What is the expected behavior? Chrome should reload your extension at the appropriate time, without you having to click something. What went wrong? You have to reload your extension manually every time you make a change. WebStore page: Did this work before? N/A Chrome version: 51.0.2704.103 Channel: n/a OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 22.0 r0 Suggested solution: - extension authors can include a file in their extension called "_reload". - if present, Chrome watches this file for changes. - whenever that file's mtime changes, Chrome reloads the extension. So the extension author can just touch that file whenever they want Chrome to reload their extension. This is a simple solution that's compatible with pretty much any toolchain, and won't interfere with existing extensions as it uses an underscored filename (which is reserved for special uses like this). Developers who don't want to use it, don't have to, so there is no watch penalty for extensions that don't want to use this feature. This StackOverflow question for how many people have this problem: http://stackoverflow.com/questions/2963260/how-do-i-auto-reload-a-chrome-extension-im-developing (The existing community-provided solutions are very imperfect.) |
|
►
Sign in to add a comment |
|
Comment 1 by sheriffbot@chromium.org
, Jul 28 2017