There’s an issue with the Elm debugger where it breaks when a large list is fetched. The project was started a year ago and the issue did not happen then because the list the API returned wasn’t that long then. I came back for some additional features recently and ran into this issue debugger runtime exception: Uncaught RangeError: Maximum call stack size exceeded · Issue #2133 · elm/compiler · GitHub (seems to be only breaking in Chrome)
Since I could develop locally otherwise, once I tracked down that it was the size if the list that caused the issue I adde a
List.take 10 before my usage of the list, which made the list small enough for the debugger to work.
I made a
TODO comment to remove this logic before shipping to production, would up forgetting and the bug ended up in front of users on prod. Of course that is my fault.
Today I was reminded of the bug another time by
megapctr on slack who asked around because of the same issue.
Several people have posted about this: Maximum call stack size exceeded when running --debug · Issue #90 · elm/browser · GitHub, here’s a PR Fix stack overflow when operating on large lists by robinheghan · Pull Request #95 · elm/browser · GitHub and some others that I don’t find right now. Anyone else ever ran into this? Is this affecting your local development badly?