Closed colinmccabe closed 7 years ago
Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!
Here is what to expect next, and if anyone wants to comment, keep these things in mind.
Related (enough that I didn't want to make a new issue):
I noticed when I accidentally provided invalid version bounds
"elm-community/html-extra": "2.2.0 <= v < 2.0.0"
that instead of erroring, elm package install
tried to remove all of the installed packages:
Some new packages are needed. Here is the upgrade plan.
Remove:
elm-lang/core
elm-lang/html
elm-lang/virtual-dom
elm-lang/websocket
Do you approve of this plan? [Y/n] n
When adjusted to the correct bounds ("elm-community/html-extra": "2.2.0 <= v < 3.0.0"
), the installation proceeds as expected:
> elm package install
Some new packages are needed. Here is the upgrade plan.
Install:
elm-community/html-extra 2.2.0
Do you approve of this plan? [Y/n] y
Added some new code that will disallow invalid bounds with nicer error messages. Thanks for the report!
Possibly related to #249
Running
elm package install
on a clean project containing only anelm-package.json
with invalid version bounds"elm-lang/html": "2.0.0 <= v < 2.0.0"
results in
Creating an empty
elm-stuff
and runningelm package install
again prints onlyPackages configured successfully!
, and creates emptyelm-stuff/exact-dependencies.json
andelm-stuff/packages
.Using Elm 0.18 Beta for Mac from this revision of the Gist: https://gist.github.com/evancz/8032a3ac6eb7a4ac8e0956ed6d386798/7f5775901120d24726e6610e8065aea5b17643da