Following Most popular elm related npm packages by usage, I wanted to try the method on Elm packages.
GitHub is not able yet to list dependents of elm packages, so I wanted to use GitHub code search to find packages declared in
elm.json files. Unfortunately, GitHub code search does not support special characters, which is quite a disappointment for a source code web site.
Without precise code search in
elm.json, there are too much false positives, so I restrained myself for now to packages used in other packages, using exact presence of packages in dependencies of others (I did not use
test-dependencies though, maybe I should have). A better way would be to locate and download all existing
elm.json files by using GithUb API then searching manually the dependents. This is quite cumbersome though due to GitHub API rate limits.
- Using only packages dependencies is very detrimental to applications oriented packages, so keep that in mind when looking at the results.
- This time I normalized the value to 100, and packages unused in others packages are not listed.
- Remember that the total usage is divided by the number of moons (28 days) since the package creation to lower the advantage for packages to be old and let new packages rank up faster. This is why for example nikita-volkov/typeclasses is quite high in the ranking, it has only two packages using it, but in less than two months since its creation.