Paste your elm.json & get a personalized checklist — no more manual docs.
The Elm 0.19.2 release brings a significant build‑time improvement — early benchmarks show reductions from 30 s to under 5 s for medium‑sized projects. Yet the migration path is fragmented: the official docs are comprehensive but scattered, and the Slack community answers one‑off questions without structured guidance. Developers waste hours cross‑referencing dependency versions, API changes, and compiler flags.
Existing solutions like manual diffing or GitHub issue searches are passive and project‑agnostic. There is no tool that reads your elm.json and tells you exactly what to do. With the Elm community at roughly 5 000–10 000 active developers and the 0.19.2 upgrade being a one‑time event, the window for a focused migration assistant is wide open — and no dedicated tool exists today.
By acting now, you skip the friction of manual migration and get a repeatable, project‑specific checklist. The signal is clear: HN discussions, Lobsters threads, and Elm Slack conversations all point to “build speed” as the #1 pain point. This is the moment to automate the boring part.
Copy the contents of your project’s elm.json file — the one that lists dependencies, source directories, and Elm version. Paste it into the input field above. No sign‑up, no uploads.
Our front‑end parser checks every dependency against the 0.19.2 ecosystem. You’ll see which packages need updates, which are already compatible, and any that are deprecated — all in under 2 seconds.
Receive a prioritized, project‑specific migration plan: from updating elm.json version constraints to adjusting import paths and recompiling. Each step includes estimated effort and links to relevant docs.
Automatically detect which of your Elm packages support 0.19.2. No more manual checks on GitHub or package.elm‑lang.org — the tool cross‑references the entire registry in real time.
Based on your project size (module count, dependency graph, source file count) we estimate how much faster your build will be after migrating — typically 4–6× improvement for projects with 20+ modules.
Receive a numbered checklist of 5–7 concrete actions, ordered by impact and dependency. Each step includes a short explanation, relevant Elm compiler flags, and links to official 0.19.2 release notes.