napcs/node-livereload

LiveReload 0.7.0 says reloading but doesn't

Closed this issue · 9 comments

What version of Livereload are you using?

v0.7.0

What OS are you using?

Windows 10

What web browser are you using? (Browser name and specific version please)

Tried in Chrome and Firefox both have same issue

Expected result

LiveReload should trigger on the page

Actual result

The livereload console says "Reloading: " etc but the page does not reload(using the sublime text livereload works so it isnt the browser)

Steps to reproduce issue

Run Commands

npm i -g livereload
livereload .
napcs commented

@DarkVamprism Hi. One more piece of info I need - Are you using the LiveReload browser extension, or did you insert the JS from the file as shown in the README?

I tried both and neither worked.

napcs commented

Thanks for the additional info. I'll see what I can find.

napcs commented

@DarkVamprism I released 0.8.0 which has updated file watching deps. Can you let me know if you're still having problems?

I just tried version 0.8.0 and see the same issue. The files say "Reloading" but the browser does no automatically refresh. I'm using the package and ran:

livereload . -p 22000 -d
napcs commented

@cmacdonnacha You've set the client to use the same port number? Are you using the browser extension or embedded JS?

I cannot reproduce this issue on Chrome or Firefox on Windows 10 with Node.js 10 LTS. Any more information you can provide would be great. Here's a quick cast of my test on Windows 10.

windows10

napcs commented

@DarkVamprism I'm not able to reproduce this on a couple of windows machines now. Is there any additional info you can give about your setup?

I am not sure if cmacdonnacha has the same issue but seeing your gif helped me see what was supposed to happen. I re-setup the project and had the same issue but noticed I wasn't getting the "Browser connected" message so I tried closing my sublime text editor and restarted the webpage and it connected.

It turns out that even though the liveReload plugin for sublime was set to disabled, it still had the server running and it caught the client preventing this plugin from being able to listen.

napcs commented

@DarkVamprism ah yea that makes sense. Great. Closing this issue.