Package Control: Install Package
in the Command Palette (Super+Shift+P)npm i -g elm
)elm-package.json
file (requires elm-oracle, which you can install with npm install -g elm-oracle
)
alt+up
or through the right-click context menualt+down
Build
just checks errors. Kudos to this tweet!Run
additionally outputs your compiled program to an inferred path.elm-package.json
or Elm Build System: …
in the Command Palette. Elm build system only requires a valid config in any ancestor directory of the active file. elm-repl
in an editor tab with syntax highlighting. elm-format
is in your PATH"elm_format_on_save": true
elm-format
on, for example elm-css based files, you can set a regex filter which will search the full filename (including the path to the file). If the regex matches, then it will not automatically run elm-format
on the file when you save. For example, the following filter would prevent automatic elm-format
on a file named elm-css/src/Css/TopBar.elm
:
"elm_format_filename_filter": "elm-css/src/Css/.*\\.elm$"
elm-oracle
installed, but completions, type signature display, and the type panel don't work
elm-oracle
is on your PATH, orelm-oracle
to the elm_paths
setting in your Elm Language Support User settingselm-format
installed, but it's not working
elm-format
is on your PATH, orelm-format
to the elm_paths
setting in your Elm Language Support User settings. Note that you can combine paths with the above, so an example might be "elm_paths": "/users/alex/elm-format:/users/alex/elm-oracle"
elm-format
on, for example elm-css based files, you can set a regex filter which will search the full filename (including the path to the file). If the regex matches, then it will not automatically run elm-format
on the file when you save. For example, the following filter would prevent automatic elm-format
on a file named elm-css/src/Css/TopBar.elm
:
"elm_format_filename_filter": "elm-css/src/Css/.*\\.elm$"
Don't know Elm? Great first step!
The following features are being worked on next:
elm-package
support. Install packages, open docs in the browser, and pull package stats from GitHubIf there's any features you'd like to see, send me an email!