-
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
No livereload with directory start #155
Comments
I just tried and things seem fine here. Can you put together a test case so that I can reproduce the issue? Thanks. 😄 |
Well, it must be something with my computer :(
|
I just ran into the same problem: # node: v5.9.0 (npm v3.7.3)
> budo --live --dir=. --debug --host localhost index.js:bundle.js
[0000] info Server running at http://localhost:9966/ (connect)
[0000] info LiveReload running on 35729
[0001] 58ms 1610B (browserify)
[0005] 7ms 1610B GET 200 /bundle.js
# Meanwhile `/bundle.js` got altered.
[0011] 3ms 1610B GET 200 /bundle.js
[0012] 1ms 1610B GET 200 /bundle.js With and without I also tried deleting all packages upgrading to Back to wzrd and manual reload for now... |
Sorry, your message slipped through the cracks of my email it seems. Can you let me know what OS you are using? I'm using the same command on the same node/npm versions and I can't reproduce any problems. I'm on OSX 10.11.4. |
Np, thanks @mattdesl. I am on: OSX 10.11.5 |
For those experiencing LiveReload issues, you can try the WIP branch here which replaces tiny-lr with a custom WebSocket backend: |
Should probably be fixed with latest 10.x release. Please open a new issue if there's any more LiveReload bugs. |
Version : "budo": "8.2.2"
Chrome 50.0.2661.86
Env: Electron: v0.37.7 - node v5.10.0
I'm using Budo with its API.
I'm running :
Path is a directory. Budo serve everything correctly. Unfortunately altering the .html or .css file does not seems to reload the content. I have to manually reload the page.
Running budo from command line :
budo --live --dir=MYPATH
works perfectly.The text was updated successfully, but these errors were encountered: