# \[FIXED\] Fixing Elm-Make 0.19 in VS Code 1.27.2

**URL:** <https://discourse.elm-lang.org/t/fixed-fixing-elm-make-0-19-in-vs-code-1-27-2/2059>\
**Category:** Learn\
**Created:** [September 26, 2018, 2:38pm UTC](https://discourse.elm-lang.org/t/fixed-fixing-elm-make-0-19-in-vs-code-1-27-2/2059 "2018-09-26T14:38:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hasimir](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/hasimir/32/2367_2.png) [@Hasimir](https://discourse.elm-lang.org/u/Hasimir)\
**Post date:** [September 26, 2018, 2:38pm UTC](https://discourse.elm-lang.org/t/fixed-fixing-elm-make-0-19-in-vs-code-1-27-2/2059/1 "2018-09-26T14:38:46Z")

</div>

Hi 🙂  
As the title says, I’m trying to have Elm 0.19 work in VS Code 1.27.2, under Ubuntu 18.04.

I managed to install the Elm relevant packages and the Format tool too. But whenever I save the file it tells me that Elm-Make is not installed.  
Searching the web I’ve found discussions of people mentioning “problems with the $PATH” or something… but I couldn’t figure out what I was supposed to do 😕

Can anyone help me?  
Thx! 😃

[EDIT]  
As a good n00b I did a stupidly n00b mistake.  
I tried writing some test elm code without a proper project.  
The moment I made a new folder and run **elm init** all was solved 😛

Meh. All is well that ends. Period.

---

<div class="post-metadata">

**Author:** ![Brian\_Carroll](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/brian_carroll/32/444_2.png) [@Brian\_Carroll](https://discourse.elm-lang.org/u/Brian_Carroll)\
**Post date:** [September 26, 2018, 3:26pm UTC](https://discourse.elm-lang.org/t/fixed-fixing-elm-make-0-19-in-vs-code-1-27-2/2059/2 "2018-09-26T15:26:47Z")

</div>

The VS Code Elm plugin doesn’t support 0.19 yet as far as I know.

Elm 0.19 has no `elm-make` executable. That’s why it’s not found. There used to be several command line tools but now there’s just one executable called `elm`. The plugin developers will need to update it.  
I’d suggest having a look at the open issues in the GitHub repo for the plugin to see what their plans are.

---

<div class="post-metadata">

**Author:** ![Hasimir](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/hasimir/32/2367_2.png) [@Hasimir](https://discourse.elm-lang.org/u/Hasimir)\
**Post date:** [September 26, 2018, 3:30pm UTC](https://discourse.elm-lang.org/t/fixed-fixing-elm-make-0-19-in-vs-code-1-27-2/2059/3 "2018-09-26T15:30:14Z")

</div>

Thx Brian 🙂  
Apparently things DO work, if one does them properly XD  
Unless this is a serendipitous “positive error” that I am somehow making 😉

---

<div class="post-metadata">

**Author:** ![bob-shelline](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/bob-shelline/32/465_2.png) [@bob-shelline](https://discourse.elm-lang.org/u/bob-shelline)\
**Post date:** [September 26, 2018, 7:36pm UTC](https://discourse.elm-lang.org/t/fixed-fixing-elm-make-0-19-in-vs-code-1-27-2/2059/4 "2018-09-26T19:36:39Z")

</div>

The plugin is actually updated at the moment to support version 0.19. If you press `cmd + ,` to open up the options and then search for “elm” you will see two relevant options. “Elm: Compiler” is for 0.19+ and needs to be set to something like `./node_modules/.bin/elm`, while “Elm: Make Command” is for 0.18 and earlier and needs something like `./node_modules/.bin/elm-make`. This will work for local Elm installations, though if you use a global installation you may need to run `which elm`/`which elm-make` to find the path you are using.

---

<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:** [October 6, 2018, 7:36pm UTC](https://discourse.elm-lang.org/t/fixed-fixing-elm-make-0-19-in-vs-code-1-27-2/2059/5 "2018-10-06T19:36:40Z")

</div>

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