That message originates in elm/parser, and the best way forwards would probably be for elm/parser to either implement it or stop exposing it, but right now it's probably on the users of elm/parser to not use it and instead provide their own implementation.
rtfeldman
commented
3 years ago
We've hit this in our app:
https://ellie-app.com/66WPxcDYHDHa1
That message originates in
elm/parser, and the best way forwards would probably be forelm/parserto either implement it or stop exposing it, but right now it's probably on the users ofelm/parserto not use it and instead provide their own implementation.