Comments (11)
@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.
Related Issues (20)
- Update chokidar HOT 4
- client can't be found HOT 3
- Failling to load livereload dependency HOT 1
- Docker + browser extension, "Cannot download livereload.js" HOT 11
- Should reload when the exact path is changed HOT 3
- livereload.js request is hanging attempting to GET through a reverse proxy connection. no debug output available. HOT 1
- Feature request: Enable error message or logging levels to trace errors to stdout if things dont work. HOT 2
- Support proxied socket URL connections when running livereload from the command line. i.e. allow definition of a public socket URL. HOT 2
- javascript code auto injected in HTML page HOT 3
- Feature request: support refreshing when an endpoint returns 200 HOT 1
- Command line for multiple path seems to be broken in 0.9.2 HOT 2
- Exclusions not working? HOT 7
- Improve documentation in README for how exclusions work
- feature request: support CORS for hosts HOT 1
- Require is not defined.
- Support configuring the interface (i.e. host) the server will listen to HOT 1
- Possible to specify a different path prefix? HOT 2
- Cannot use multiple node-livereload servers on one page HOT 1
- ENOSPC: System limit for number of file watchers reached
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from node-livereload.