I start with my conclusion: use elm-json for the elm packages. Now, my story:
Yesterday, a member of my team joined to my elm project to learn the project and help me, but…. when i started the elm make command, surprise, problem with the dependencies! The problem was this package:
"Skinney/murmur3": "2.0.8"
The author removed the source (or it moved), the simple solutions is copy my package directory and give it to my collegue, but it’s no final solution.
The accused package is used from
"rtfeldman/elm-css": "15.1.0"
The last version of elm-css (16.1.0) don’t depende from murmu3 so the solution is upgrade the elm-css.
I tryed it, removing from the elm.json and run
elm install rtfeldman/elm-css
I have always an dependecies error. So, i chat on slack with the community and they suggested me to use elm-json. With elm-json i try to uninstall
elm-json uninstall rtfeldman/elm-css
but I see an message error, there are other package stephenreddek/elm-range-slider
that depends from this elm-css in version 15.1.0, so at the end there are my steps:
npm -g install elm-json
elm-json uninstall rtfeldman/elm-css
elm-json install rtfeldman/elm-css@16.1.0
elm-json uninstall stephenreddek/elm-range-slider
elm-json install rtfeldman/elm-css@16.1.0
Conclusion: use elm-json for the elm packages.