livereload --debug disables file watcher about node-livereload HOT 11 CLOSED

@dotnetCarpenter Oops. I didn't catch this. This is actually pointed out in the README file. When you use the options, you have to specify the path.

livereload . --debug

It's because of the way the options are parsed and it goes back to before I took this project over, and I always forget about this.

I just made a backwards compatible fix coming for this that eliminates that issue by properly parsing out the path option, but that's what's happening to you.

If that addresses this, please close this. I'll tag this issue when the new release is out. So sorry for the trouble!!

from node-livereload.

@dotnetCarpenter Version 0.9.2 is out and it has this fix added. Thanks for your patience.

from node-livereload.

I actually have my repo for you, in case you want that as an easier way to reproduce.
https://github.com/Firefund/firefund-lfs/tree/master/design/gradient_donut

from node-livereload.

Hi @dotnetCarpenter. Sorry for the delayed reply.

This is certainly a strange one. Before we dig too deep, can we remove npx from the mix here? Install livereload globally please, with npm install -g livereload and run it directly. Since npx is a wrapper, I suspect there's something else going on here.

from node-livereload.

I get the exact same result when I run livereload --debug directly from the terminal.

I edited index.html and without the --debug flag it worked flawlessly (reloaded) but not at all with the --debug flag.

from node-livereload.

@dotnetCarpenter I think I know what's going on. When livereload writes to STDOUT your shell may be halting its execution. There are some shells that default to this behavior.

Try issuing this command first:

stty -tostop

This instructs the shell to continue processing even if the program writes to STDOUT.

from node-livereload.

It doesn't seem to make any difference. I am using Windows Terminal Version: 1.4.3243.0.

But I notice that the path ends in "--debug" when I add the --debug flag.

Starting LiveReload v0.9.1 for /home/dotnet/projects/firefund/firefund-lfs/design/gradient_donut/--debug on port 35729.
Watching /home/dotnet/projects/firefund/firefund-lfs/design/gradient_donut/--debug...

/home/dotnet/projects/firefund/firefund-lfs/design/gradient_donut/--debug

console.log "Starting LiveReload v#{version} for #{path} on port #{port}."

That might explain why server.watch(path) is not working.

from node-livereload.

This works great! I didn't see Specify the path when using the options. in the README...

I also can not see your commit for the fix but I've changed my bash script. I hope you commit your fix for the next release. I might not be the only one who does not closely read the README.

Thank you for all your support and for maintaining livereload!

Happy new year!

from node-livereload.

@dotnetCarpenter yea the next release will definitely have the options fix in it; it's been bugging me for far too long and I finally found the time to investigate what the heck was going on. I've not pushed the branch to GH yet.

from node-livereload.

Hi @napcs, is there any way I can speed this along? I got bitten by this bug again, just now.

I hope you are good and I don't mean to stress you. Just curious if I can help?

from node-livereload.

@dotnetCarpenter thanks for the ping. I've already got a branch with the updated code. I'm trying to resolve #147 and #148 before I push the next version though.

from node-livereload.