Great video about a great tool. There is only one thing holding me back from moving from elm-live to elm-watch and that is the proxy functionality to reach the back-end. I know you do not want to extend elm-watch with all kind of none-core functionalities. But do you know a good tool to setup a proxy to the back-end that could work alongside elm-watch?
Just wanted to say elm-watch is really exellent, thanks for making it.
We already have a build that runs in a loop using webpack to make the dev/prod builds. However, even with that running I will typically run elm-watch alongside, like this npx elm-watch hot. As I code the Elm side, I tend to look at the output of that over our proper build, since it is very fast and easier to read.