33 stable releases

5.7.0 Dec 22, 2023
5.6.6 Jul 30, 2023
5.6.4 Apr 15, 2023
5.6.3 Sep 3, 2022
4.3.4 Nov 22, 2020

#490 in Parser implementations

Download history 58/week @ 2023-12-22 74/week @ 2023-12-29 74/week @ 2024-01-05 174/week @ 2024-01-12 184/week @ 2024-01-19 98/week @ 2024-01-26 328/week @ 2024-02-02 187/week @ 2024-02-09 153/week @ 2024-02-16 175/week @ 2024-02-23 135/week @ 2024-03-01 84/week @ 2024-03-08 73/week @ 2024-03-15 45/week @ 2024-03-22 159/week @ 2024-03-29 109/week @ 2024-04-05

392 downloads per month
Used in 3 crates (2 directly)

MIT license

46K SLoC

C 45K SLoC // 0.0% comments JavaScript 688 SLoC // 0.0% comments Scheme 76 SLoC // 0.1% comments Rust 38 SLoC

Build Status

Elm tree sitter

Why am I doing this?

I believe that Elm would greatly benefit from better tooling, the ultimate goal is to write a language server integration. This is a possible building block for that.

What it brings to the table:

  • Very fast parsing, should enable parsing on each keystroke.
  • Resilient, even if you use wrong syntax, most of the file should still be recognized alright.
  • Should also be useful to the elm atom maintainers, as atom is using tree sitter as the new default for code highlighting (our ast might be too expressive). Highlight implementation still needs to be done if wanted.

What is this tested with?

This is tested against the tests included in the repo and:

So it should work fine for a fair amount of code. What's not tested right now is behavior in error cases.


Very very big thanks goes out to @klazuka and the people of intellij-elm as I basically stole how they're creating their parser minus the GLSL implementation.

Want to help?

Help writing some tests or simply find valid elm files, that fail parsing. Test are located in the test folder and separated in parser tests and highlighting tests.


~73K SLoC