ellie VS elm-review

Sorry I'm not being helpful (in that, I dont have a solution for you) but it would be great if you could put this up as a working demo on Ellie (https://ellie-app.com/).

There is an online editor, named Ellie, to play with the language without the need to install anything on your machine. Ellie permits to install dependencies for your code, so you can prototype an entire project with it.

After that point I started looking into how Elm works from the web dev perspective with resources like Elm in Action and Frontend Masters courses (first working in ellie-app-for-elm-dev then upgrading to vite-elm-template).

I can still give you some pointers here. First I'd suggest you read the elm guide: https://guide.elm-lang.org/ It's the best place to start with elm. When you have a question about any specific subject, you should head to the slack, or ask a question on the elm discourse: https://discourse.elm-lang.org/ . The best way to get a useful answer, is to have a concrete question, and to prepare an example of what is wrong on Ellie (https://ellie-app.com). As such people can modify your Ellie to answer you.

You can paste it to Ellie for testing

req: Request { bodyUsed: false, headers: Headers { accept: "*/*", "accept-encoding": "gzip, deflate, br", "accept-language": "en-US,en;q=0.9,la;q=0.8", connection: "keep-alive", host: "localhost:8000", origin: "https://ellie-app.com", "sec-ch-ua": '"Chromium";v="94", "Google Chrome";v="94", ";Not A Brand";v="99"', "sec-ch-ua-mobile": "?0", "sec-ch-ua-platform": '"macOS"', "sec-fetch-dest": "empty", "sec-fetch-mode": "cors", "sec-fetch-site": "cross-site", "user-agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/94.0.4..." }, method: "GET", redirect: "follow", url: "http://localhost:8000/" } ourAnswer: Response { body: ReadableStream { locked: false }, bodyUsed: false, headers: Headers { "content-type": "text/plain;charset=UTF-8" }, ok: true, redirected: false, status: 200, statusText: "", url: "" }

https://builtwithelm.co/ lists some, but not sure what you consider large.

Not sure if you would categorize this as dev tool https://github.com/erkal/kite

And ellie certainly might be a dev-tool, but not a toy https://github.com/ellie-app/ellie

It uses devbox, Elm 0.19.1, the latest Elm packages (in particular elm/http 2.0.0), elm-review, Caddy, a sprinkle of Dart Sass, and a handful of Bash scripts (one of them being a deployment script). It uses elm test and features tests for key data structures.

A special shout out to Elm review which has inspired how reanalyze reports code that's transitively dead.

The Elm community has an unofficial linter (called elm-review), which can be used to check your code for potential bugs or mistakes, or highlight a better way to write Elm. Unlike elm-format (and more similar to tools like ESLint), elm-review does not come with any default rules to follow:

elm-review: https://package.elm-lang.org/packages/jfmengels/elm-review/latest/

Glad to see more posts on Elm out there, it really is a great language and ecosystem! Like any large project, it has some issues, but in my day-to-day writing code I have never had as much fun, or had as much confidence that my code does what it says on the tin, as I have with Elm.

I wanted to give a shout out to one of Jeroen's other projects in the Elm ecosystem, elm-review (https://package.elm-lang.org/packages/jfmengels/elm-review/l...), it is an excellent linter/fixer and allows writing your own rules as well.

For technical debt and other code-base maintenance, I'd suggest using elm-review.