Håkon Rossebø

@halohalospecial - I've created an issue on how we can try to join forces on creating a common language server for Elm here - https://github.com/Krzysztof-Cieslak/vscode-elm/issues/137. Hope you can join in...

Created #230. So, should we continue this issue, or create separate issues, one for creating a boilerplate from the time-tracker, and separate issues for each upstream template we want to...

I don't know the details, but there was a long discussion group thread [here](https://groups.google.com/forum/#!msg/elm-discuss/8Q2xwRh6UYc/UTkiQCIBAwAJ) @knewter also has a series of this topic on Dailydrip, with some resources on this [page](https://www.dailydrip.com/topics/elm/drips/preparing-for-web-components)...

The list was part of the long discussion - message link here: https://groups.google.com/d/msg/elm-discuss/8Q2xwRh6UYc/oP4CRuLiAQAJ

Thanks - fixed. Should work as expected when cache is expired/refreshed.

A CLI with editor integrations seems like a very useful tool. Always difficult having enough time :)

Not sure if have time to help out, but you could create some issues if you want help with specific features.

This is a great find. I assume by modularising, we could still support LSP as one of the interfaces exposed from the language server?

@ringods - Thanks for your contributions. I'm the same person starting that issue, working on VSCode-elm and feeling the pain points of re-inventing the wheel to parse some Elm code.