# Elm-watch 1.1.0 released!

**URL:** <https://discourse.elm-lang.org/t/elm-watch-1-1-0-released/8738>\
**Category:** Show and Tell\
**Created:** [October 29, 2022, 2:17pm UTC](https://discourse.elm-lang.org/t/elm-watch-1-1-0-released/8738 "2022-10-29T14:17:05Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![lydell](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/lydell/32/178_2.png) [@lydell](https://discourse.elm-lang.org/u/lydell)\
**Post date:** [October 29, 2022, 2:17pm UTC](https://discourse.elm-lang.org/t/elm-watch-1-1-0-released/8738/1 "2022-10-29T14:17:05Z")

</div>

🎉 I just released elm-watch 1.1.0, with a bunch of edge case fixes and a couple of new features! 🎉

- The biggest feature is the opt-in **error overlay in the browser,** with clickable error locations!
- You can now move the browser UI to a different corner.

I go through those two features in more detail in this video:

[![](https://img.youtube.com/vi/Gde5D1ImZPI/maxresdefault.jpg "What’s new in elm-watch 1.1.0") ](https://www.youtube.com/watch?v=Gde5D1ImZPI)

Full changelog:

> **[Release 1.1.0 · lydell/elm-watch](https://github.com/lydell/elm-watch/releases/tag/v1.1.0)**
>
> Note: If you use elm-watch together with run-pty, make sure to update run-pty to 4.0.2 or later!
> 
> New features
> 
> 
> Added: An opt-in error overlay in the browser, with clickable error locations. When ...

> **Note:** If you use elm-watch together with [run-pty](https://github.com/lydell/run-pty), make sure to update run-pty to 4.0.2 or later!

---

<div class="post-metadata">

**Author:** ![jfmengels](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/jfmengels/32/3124_2.png) [@jfmengels](https://discourse.elm-lang.org/u/jfmengels)\
**Post date:** [October 29, 2022, 2:45pm UTC](https://discourse.elm-lang.org/t/elm-watch-1-1-0-released/8738/2 "2022-10-29T14:45:16Z")

</div>

These are all really cool and useful features! Amazing job!

Loved the intro to the video as well 😄

---

<div class="post-metadata">

**Author:** ![dirkbj](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/dirkbj/32/3162_2.png) [@dirkbj](https://discourse.elm-lang.org/u/dirkbj)\
**Post date:** [November 1, 2022, 4:47pm UTC](https://discourse.elm-lang.org/t/elm-watch-1-1-0-released/8738/3 "2022-11-01T16:47:14Z")

</div>

Well done! These are great additions. Excited to see the next update. 😉

---

<div class="post-metadata">

**Author:** ![Bjorn\_van\_den\_Broek](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/bjorn_van_den_broek/32/2857_2.png) [@Bjorn\_van\_den\_Broek](https://discourse.elm-lang.org/u/Bjorn_van_den_Broek)\
**Post date:** [November 1, 2022, 5:58pm UTC](https://discourse.elm-lang.org/t/elm-watch-1-1-0-released/8738/4 "2022-11-01T17:58:48Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![lydell](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/lydell/32/178_2.png) [@lydell](https://discourse.elm-lang.org/u/lydell)\
**Post date:** [November 2, 2022, 5:35am UTC](https://discourse.elm-lang.org/t/elm-watch-1-1-0-released/8738/5 "2022-11-02T05:35:12Z")

</div>

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](https://github.com/lydell/elm-watch/blob/main/example/dev-server.js).

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):

> <https://github.com/lydell/elm-watch/blob/b645c566ad430138128a67e047f2e91da1f30c81/example/dev-server.js#L196-L218>

I recently copied that example and reduced it to just one app when I needed it for a project:

> <https://github.com/lydell/elm-app-url/blob/2087c299f95dee5c66b397fb35c90196a6b7892b/dev-server.js#L95>

---

<div class="post-metadata">

**Author:** ![Bjorn\_van\_den\_Broek](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/bjorn_van_den_broek/32/2857_2.png) [@Bjorn\_van\_den\_Broek](https://discourse.elm-lang.org/u/Bjorn_van_den_Broek)\
**Post date:** [November 2, 2022, 8:00pm UTC](https://discourse.elm-lang.org/t/elm-watch-1-1-0-released/8738/6 "2022-11-02T20:00:07Z")

</div>

Thanks for your extensive reply. I highly appreciate it. I will move to elm-watch

---

<div class="post-metadata">

**Author:** ![rupert](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/rupert/32/1775_2.png) [@rupert](https://discourse.elm-lang.org/u/rupert)\
**Post date:** [November 3, 2022, 9:52am UTC](https://discourse.elm-lang.org/t/elm-watch-1-1-0-released/8738/7 "2022-11-03T09:52:41Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex035/uploads/elm_lang/original/1X/50a05e53677a2c3b47776d7abd0f113eb50193a1.png) [@system](https://discourse.elm-lang.org/u/system)\
**Post date:** [November 13, 2022, 9:53am UTC](https://discourse.elm-lang.org/t/elm-watch-1-1-0-released/8738/8 "2022-11-13T09:53:33Z")

</div>

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.