-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"LiveReload disabled because it could not find its own <SCRIPT> tag" after a handful of saves #195
Comments
Um, OK, the first few force-reloads didn't fix this, and now, it somehow fixed itself. Never mind, sorry for the bother... |
Er...it's very intermittent. I'll make several changes to a file, and each save triggers a reload OK, and then suddenly a save will cause that error and no further live reloading will happen until I can get the browser to reload the page from scratch. |
Sometimes, that "getting the browser to reload the page from scratch" takes up to 6 "shift+clicking the reload icon". Firefox 50.1.0. |
Really strange. I'm just adding a character to a string, to test this. The past three runs took 3, then 2, then 5 saves before this issue happened. |
Thanks for testing — so basically it's just not very reliable for you on Windows? Can you try this script to let me know what events are firing for you?
require('budo').cli(process.argv.slice(2), {
live: true
}).on('watch', function (ev, file) {
console.log('file changed', file);
}).on('update', function () {
console.log('new bundle');
}); Save it as node dev.js index.js When you save the I've been planning on overhauling the LiveReload backend at some point (#194) which may alleviate some of this (it works pretty well for me on OSX but I have heard complaints on other platforms). |
Thanks for your help! Unfortunately when I do the above, I get the error |
Ah — for the above script to work you will need to install it locally I've made some progress on the live reload backend, you can also test it like this: npm install mattdesl/budo#feature/livereload-rework -g |
OK, making progress, but now budo serves up a page saying, That fsevents gets a warning really often using npm, but it always says 'optional'. I'm on Windows at this particular moment but IIRC I also get it on Linux Mint. Makes sense now that I look at the warning more closely, since neither are Darwin:
(I got that installing budo, but no other warnings or errors) |
This is also true if I revert the install back from the feature branch. |
Ok, I've tested the LiveReload branch on my Windows 10 with node 6.9.4 and fixed a couple small issues, seems to be working alright now. Hopefully the latest version will work for you: npm install mattdesl/budo#feature/livereload-rework -g (Or, if you are running |
That seems to work great, I made about 20 changes, and every one of them worked. Thanks! |
(I would close but I guess you want to leave it open until you merge the branch, etc.) |
I'm actually having the same issue on MacOSX 10.11.6 (El Capitan), if it can helps. |
This should be all merged into budo@10. Thanks! |
That's what the console says when I load
/
. My setup:budo --live --open index.js
win7x64sp1
nodejs 7.3.0
The text was updated successfully, but these errors were encountered: