# Revive deleted code of Elm packages

**URL:** https://discourse.elm-lang.org/t/revive-deleted-code-of-elm-packages/8928
**Category:** Request Feedback
**Created:** [February 4, 2023, 7:51am UTC](https://discourse.elm-lang.org/t/revive-deleted-code-of-elm-packages/8928 "2023-02-04T07:51:08Z")
**Posts on this page:** 1
**Showing post:** 7

<div class="post-metadata">

### Author: ![rupert](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/rupert/32/1775_2.png) [@rupert](https://discourse.elm-lang.org/u/rupert)
#### Post date: [February 4, 2023, 9:44am UTC](https://discourse.elm-lang.org/t/revive-deleted-code-of-elm-packages/8928/7 "2023-02-04T09:44:45Z")

</div>

On the Elm dependencies analyzer - this tool was useful to me a number of times when my elm.json got messed up:

> [@Dependencies analyzer for application elm.json](https://discourse.elm-lang.org/t/dependencies-analyzer-for-application-elm-json/2654):
>
> As I havn’t yet seen any solution for solving elm.json dependency conflicts, I decided to try creating a small app for this, while waiting for someone else to come up with a proper solution. This is my first Elm app of over 1000 lines, so probably full of bugs. grin The app parses given elm.json, then loads information about related packages and their versions, and shows a table of the versions of elm.json and all newer versions, including all indirect packages. There is no automatic conflic…

Are we going to miss this (haven’t used it for ages now)? Or is this now stuff that `elm-json` can do?

---

_[View the full topic](https://discourse.elm-lang.org/t/revive-deleted-code-of-elm-packages/8928)._