4 ms·

I would argue the opposite! The elm slack is very active with people who frequently contribute to the ecosystem. I don't think the "a lot of libraries aren't u

I would argue the opposite! The elm slack is very active with people who frequently contribute to the ecosystem. I don't think the "a lot of libraries aren't updated to the last lang version" is true, the vast majority are. Debugging elm-JS interactions is not really a problem when using the standard interop methods of ports and webcomponents. It's just not something that comes up often. Source: have been writing elm professionally for the last 2 and a half years.

folex 5y ago
Disclaimer: I'm just describing an annoying technical problem, it's not a blocker for the use of Elm. Elm _is_ great :) I have been using Elm for a kinda-simple project on my work: dashboard for microservices, deployment configs, nodes, etc. One of the biggest time-drains was debugging JS-Elm port interactions, looking whether there is a mismatch in types. Cuz the error looks like this: Elm eventreceiver failed: Error: Trying to send an unexpected type of value through port `collectPeerInfo`: [object Object] I know of no way of even looking into that `[object Object]`. Simply logging its fields would already be a relief, lest telling what field/type caused the error.