The APIs between elm/http 1.0 and 2.0 changed a lot. This shim consumes elm/http 2.0 and exposes an API that's mostly compatible with elm/http 1.0
- Use elm-json to find out if any packages are preventing you from upgrading.
$ elm-json install elm/http@2.0.0
-- NO VALID PACKAGE VERSIONS FOUND ---------------------------------------------
Because NoRedInk/elm-string-conversions 1.0.0 depends on elm/http
1.0.0 <= v < 2.0.0 and this project depends on elm/http 2.0.0,
NoRedInk/elm-string-conversions 1.0.0 is incompatible with this project.
And because this project depends on NoRedInk/elm-string-conversions 1.0.0,
no valid set of package versions could be found.
- Copy the source code of any of those packages directly into your codebase, and, remove the packages from your
elm.json
- Upgrade to elm/http 2.0
elm install elm/http
- In your code base as well as the packages copied over, replace
import Http
withimport Http.Legacy as Http
- Done!
- This doesn't support
Http.Progress
- This hasn't been tested