You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many thanks for making this helpful package. I had a question.
I have a Nodejs backend that is serving a html file compiled from Elm. I have the server running on one port and elm-live running on another port successfully, but what I'd like is to be able to run both on the same port. At the moment when I try this, I have to refresh the page to see the elm changes. How can I achieve this?
Thanks
The text was updated successfully, but these errors were encountered:
So technically, elm-live takes two ports to work – one for serving static files, another with a LiveReload server pushing info about updates to the browser. The static HTML file gets a JS snippet injected via inject-lr-script. That’s how the browser gets the heads up that it’s time to reload.
At the moment the port at which LiveReload is being served is hidden away in the internals. What springs to my mind is to expose a --livereload-port=PORT option where you can set that port yourself. And with control over that, you can take care of serving the snippet yourself. Does that sound good?
Many thanks for making this helpful package. I had a question.
I have a Nodejs backend that is serving a html file compiled from Elm. I have the server running on one port and elm-live running on another port successfully, but what I'd like is to be able to run both on the same port. At the moment when I try this, I have to refresh the page to see the elm changes. How can I achieve this?
Thanks
The text was updated successfully, but these errors were encountered: