Merge pull request #17 from supermario/configure-compiler

Allow user to configure an alternative Elm compiler

Author: ryan-haskell

package.json

@@ -40,13 +40,13 @@
         "command": "elmLand.htmlToElm",
         "enablement": "false"
       },
-      { 
+      {
         "category": "Elm Land",
         "title": "Install Elm",
         "command": "elmLand.installElm",
         "enablement": "false"
       },
-      { 
+      {
         "category": "Elm Land",
         "title": "Install elm-format",
         "command": "elmLand.installElmFormat",
@@ -112,6 +112,12 @@
             "description": "Enable the 'HTML to Elm' feature",
             "type": "boolean",
             "default": true
+          },
+          "elmLand.compilerFilepath": {
+            "order": 7,
+            "description": "The path to your Elm compiler",
+            "type": "string",
+            "default": "elm"
           }
         }
       }
@@ -151,4 +157,4 @@
     "terser": "5.16.3",
     "typescript": "4.9.4"
   }
-}
+}

src/features/error-highlighting.ts

@@ -128,10 +128,12 @@ const Elm = {
     const promise: Promise<ParsedError | undefined> =
       new Promise((resolve, reject) => {
         const isWindows = process.platform === 'win32'
+        const compiler = vscode.workspace.getConfiguration('elmLand').compilerFilepath;
+
         // This uses `spawn` so that we can support folders with spaces in them
         // without having to think about escaping.
         const child = child_process.spawn(
-          'elm',
+          compiler,
           [
             'make',
             // `shell: true` is needed on Windows to execute shell scripts (non .exe files).