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?
Personally, I donโt use a tool for proxying โ I write a little bit of Node.js code to have full control. You can see that in the example dev server.
Specifically, here is a function for proxying a backend (you could simplify it to always go to 127.0.0.1 but to a certain port):
I recently copied that example and reduced it to just one app when I needed it for a project:
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.