Not by hand (thank goodness). I made an elm-review-bot that is designed to run elm-review rules against Elm packages. It is hosted with Lamdera and is 100% written in Elm (the only things that aren’t Elm is a
.gitignore and a
For now it only uses NoUnused.Dependencies. When someone publishes a new version of their package, it checks for unused dependencies in that package and if it finds any, it creates a pull request (here’s an example). This is to help reduce dependency conflicts for the end user*.
Some future things this bot could do are:
- Fix incorrect Elm version ranges
- Warn if any dependencies for a package get renamed or removed
- Make sure that all the types used by exposed functions are also exposed
- Check for dead links in documentation
In the long term I hope that the compiler will do some of these checks but in the meantime, hopefully this bot can improve the package ecosystem a little bit.
*One thing I’m not sure about is if pull requests should be made when there’s only unused test dependencies. Test dependencies don’t affect anyone else but maybe it’s still useful to get rid of the ones you aren’t using? Or maybe it’s just annoying to be bothered with that?