Elm has been going strong among Elixir users, including a bunch of influencers.

I personally haven't tried it out of personal preference and instead had a great experience coupling Vue with a Phoenix backend.

Bucklescript works fantastic in the Elixir system (I have a bucklescript-tea library that maps Elm code 'almost' verbatum to Bucklescript code too).

There is an ElixirScript project in current dev, still early but usable, that compiles Elixir code to javascript too.

Elm works very well with Elixir[0]

[0] https://www.dailydrip.com/topics/elixirsips/drips/phoenix-an...

In what way does Elm work better with Phoenix than, say, with Rails or Django?

For me it was that the mindsets of Elm and Elixir were very similar. Create small functions that accept data, and emit data, sometimes create a message with some data attached to it. Using pattern matching is very similar between both languages for matching on message types and shape. Also both languages share a nearly identical pipe operator, which influences the building of very strait forward function pipelines for transforming input or data into responses and output.

Not really any 'build' way, but the 'patterns' of it are more similar in that being immutable, functional, and single-owner languages.

ClojureScript itself fits wonderfully in Elixir/Phoenix land. :)

Never thought about that, but it makes sense :)