-
Notifications
You must be signed in to change notification settings - Fork 683
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
Any option for live-reloading? #271
Comments
@leo what do you think about this feature request? I'm not sure having it in |
I think this is too much for core. People can wrap |
hi guys, I came here looking for live-reloading functionality. What CLI apps would you suggest as the best alternative that can do |
@revelt a bit late to the party but there's browser-sync |
i think reloading is important too. maybe a cli version of live reload |
There are several options out there, but none suited my purpose, so I made one. https://github.com/shannonmoeller/livery {
"scripts": {
"start": "serve"
"watch": "lr | serve"
}
} {
"scripts": {
"dev": "run-p watch-*",
"dev-serve": "serve web",
"dev-watch": "lr 'web/assets/**/*.{css,js}'"
}
} |
I wanted to understand how live reloading actually worked once. So I tried rolling my own in a determined zero dependency fashion with the aim of learning as mush as possible. I hit a wall pretty quick at the web socket connection, implementing this myself was not something I wanted to do so I searched for an alternative method for the dev server to communicate with the browser. I stumbled across Now all that remains to be done by the server when
I ended up adding this feature to my own little dev server and it has been working well so far. Recently I came back to use Would you be interested in me making a PR that includes the above implementation to see how it might look? I agree with @leo that a full blown web socket implementation would be too much for core.. but this approach offers quite a bit of bang for its buck. |
Any option for live-reloading?
Something like this? https://github.com/tapio/live-server
The text was updated successfully, but these errors were encountered: