"LiveReload disabled because it could not find its own <SCRIPT> tag" after a handful of saves

Question

"LiveReload disabled because it could not find its own <SCRIPT> tag" after a handful of saves

Closed this issue 7 years ago · 14 comments

That's what the console says when I load /. My setup:

budo --live --open index.js
win7x64sp1
nodejs 7.3.0

Answer 1 · 2017-01-05T20:29:23.000Z

Um, OK, the first few force-reloads didn't fix this, and now, it somehow fixed itself. Never mind, sorry for the bother...

Answer 2 · 2017-01-05T20:31:21.000Z

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.

Answer 3 · 2017-01-05T20:32:19.000Z

Sometimes, that "getting the browser to reload the page from scratch" takes up to 6 "shift+clicking the reload icon". Firefox 50.1.0.

Answer 4 · 2017-01-05T20:35:04.000Z

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.

Answer 5 · 2017-01-05T22:23:02.000Z

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?

dev.js

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 dev.js and then, instead of running budo, use:

node dev.js index.js

When you save the index.js file it shoould say "new bundle" and when you save a CSS or HTML file in the same directory it should say "file changed" with the path. If the terminal isn't printing those, it means Chokidar (file watching) is the problem. If the terminal is reliably printing that, but the page isn't reloading reliably, it means tiny-lr (LiveReload) is the problem.

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).

Answer 6 · 2017-01-06T06:32:52.000Z

Thanks for your help! Unfortunately when I do the above, I get the error Cannot find module 'budo' even though I installed it globally with npm. The budo command does work on the command line though. I was using it in this context: https://github.com/lhorie/mithril.js/blob/rewrite/docs/installation.md#live-reload-development-environment (which uses the command-line rather than inclusion in a js script)

Answer 7 · 2017-01-06T23:03:32.000Z

Ah — for the above script to work you will need to install it locally npm install budo. You don't need to save it to your package.json as long as you install it in a directory that has a package.json. The script is just to test to see where the problem is (live reload vs chokidar).

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

Answer 8 · 2017-01-07T06:28:13.000Z

OK, making progress, but now budo serves up a page saying,
"Cannot find module 'fsevents'
myproj\node_modules\chokidar\lib"

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:

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\ch
okidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@
1.0.17: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"
})

(I got that installing budo, but no other warnings or errors)

Answer 9 · 2017-01-07T06:30:11.000Z

This is also true if I revert the install back from the feature branch.

Answer 10 · 2017-01-12T22:03:50.000Z

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 budo in a package.json "scripts" field, make sure to save it locally with --save or --save-dev)

Answer 11 · 2017-01-14T05:13:40.000Z

That seems to work great, I made about 20 changes, and every one of them worked. Thanks!

Answer 12 · 2017-01-14T05:14:10.000Z

(I would close but I guess you want to leave it open until you merge the branch, etc.)

Answer 13 · 2017-02-20T17:20:22.000Z

I'm actually having the same issue on MacOSX 10.11.6 (El Capitan), if it can helps.
Using the livereload-rework branch fixes it.

Answer 14 · 2017-04-21T16:00:05.000Z

This should be all merged into budo@10. Thanks!