Closed sentience closed 4 years ago
Our work-around for this for now is to manually edit elm.json to remove elm-explorations/test
from our indirect dependencies after running elm.json.
Hey @sentience :wave:
This looks normal to me. y0hy0h/ordered-containers
v1.0.0 depends on elm-explorations/test
, which means that your project indirectly depends on elm-explorations/test
, which warrants it being (also) in the indirect dependencies.
You didn't explicit why you were removing it manually, but I am guessing it is because elm-test
will crash? If so, I already raised this issue here where @zwilias responded (correctly in my opinion) that the "one at fault" is elm-test
. If you tried bumping the dependencies yourself with elm install
, then you'd have that indirect dependency too.
I have since then raised the issue over at rtfeldman/node-test-runner
(https://github.com/rtfeldman/node-test-runner/issues/423) but I haven't had the chance to try and solve the issue.
Another workaround would be for you to upgrade y0hy0h/ordered-containers
to v2, where it does not depend on elm-explorations/test
anymore.
Great bug report, thank you so much!
What @jfmengels mentioned above is a pretty good summary of the current state. Having the dependency "twice" is technically correct. The incompatibility this causes with elm-test
is a shame, but I've made the decision not to work around bugs in non-core tools. Since elm
has the same behaviour as elm-json
, here, I feel like mirroring what elm
does in this situation is the better way forward.
Hope you managed to get around it by upgrading your dependency, tho! :)
Initial elm.json:
Ran
yarn elm-json upgrade --yes ./path/to/elm.json
.Console output:
Resulting elm.json:
We've been seeing this consistently with elm-json 0.2.6, and we're still seeing it with 0.2.7.