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
CSS Live reload stopped working with budo 10 #231
Comments
Is there any way I can reproduce this on my end? |
@mattdesl yes!
Then open http://localhost:9966/ in your browser and edit/save a SCSS file in Does that help? |
Thanks. Here is a simple fix for you: Use
The reason is a bit complex, and it's definitely a bug or issue with budo, but I'm not sure yet how to solve it cleanly. Here's what's happening: When a file, like Multiple static directories (the ability to do multiple Maybe one option would be to, in the case of multiple I'll have to brew on this a bit more... any suggestions are welcome, though. |
Ah, that makes sense! Thanks a lot for taking a look 🙂 The suggested workaround seems to do the trick! 👍 |
Hi. We're using budo for http://github.com/threema-ch/threema-web. When upgrading from budo 9 to 11, CSS live reloading stopped working. I tested a bit with different versions, and 10.0 was the first version that broke live reload for me.
This is how we invoke budo:
When starting the server, the following is logged to the terminal:
I can see that the live reload WebSocket is opened. In the Chrome inspector I can also see that every time I change a CSS file, I get a new message:
However, no reloading takes place.
This is what the WS messages looked like with Budo 9:
Any ideas what the reason could be?
I wonder whether the problem could be that the /public/ prefix is added as prefix, but I include the CSS files without that prefix in my HTML file (which works because of the
-d public
argument).The text was updated successfully, but these errors were encountered: