Unfortunately, some piece of software needs to run and send messages to the reload extension. In the previous post, that software was a command running on save in VS Code that opened a URL (reload.extensions), and in this post, some sort of build system (Gulp in the example) watches for file changes and then sends a message to the extension's server (see this code) to trigger the reload.
You can use another build system, but that will require some customization from the post's Gulpfile.
i was thinking that but im not sure why the original extension, not the @JeromeDane one, is working for me. i was using the run on save previously but i have that disabled and the reload extension extension disabled as well. 🤷♂️
looks like it was only half working. the background script wasnt being reloaded. my bad.
Thanks!
Unfortunately, some piece of software needs to run and send messages to the reload extension. In the previous post, that software was a command running on save in VS Code that opened a URL (reload.extensions), and in this post, some sort of build system (Gulp in the example) watches for file changes and then sends a message to the extension's server (see this code) to trigger the reload.
You can use another build system, but that will require some customization from the post's
Gulpfile.i was thinking that but im not sure why the original extension, not the @JeromeDane one, is working for me. i was using the run on save previously but i have that disabled and the reload extension extension disabled as well. 🤷♂️looks like it was only half working. the background script wasnt being reloaded. my bad.
Maybe you're on an older version of Chrome?
nah im on stable: Version 72.0.3626.119 (Official Build) (64-bit). odd.