Problem in dependency evancz/url-parser 2.0.1 -- Navigation 2.1.0 breaks the compile

[RobertFischer]

Problem in dependency evancz/url-parser 2.0.1                       

The elm-package.json constraints of 'evancz/url-parser' are probably
letting too much stuff through. Definitely open an issue on the relevant github
repo to get this fixed and save other people from this pain.

In the meantime, take a look through the direct dependencies of the broken
package and see if any of them have had releases recently. If you find the new
thing that is causing problems, you can artificially constrain things by adding
some extra constraints to your elm-package.json as a stopgap measure.

Detected errors in 1 module.  

[process-bot]

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.

[RobertFischer]

Here's my elm-package.json.

{
    "version": "0.0.1",
    "summary": "helpful summary of your project, less than 80 characters",
    "repository": "https://github.com/user/project.git",
    "license": "UNLICENSE",
    "source-directories": [
        "."
    ],
    "exposed-modules": [],
    "dependencies": {
        "Bogdanp/elm-route": "4.0.0 <= v < 5.0.0",
        "elm-community/maybe-extra": "3.0.0 <= v < 4.0.0",
        "ccapndave/elm-update-extra": "3.0.0 <= v < 4.0.0",
        "elm-lang/core": "5.1.1 <= v < 6.0.0",
        "elm-lang/html": "2.0.0 <= v < 3.0.0",
        "elm-lang/http": "1.0.0 <= v < 2.0.0",
        "elm-lang/navigation": "2.1.0 <= v < 3.0.0",
        "evancz/url-parser": "2.0.1 <= v < 3.0.0",
        "gdotdesign/elm-ui": "1.2.1 <= v < 2.0.0",
        "krisajenkins/remotedata": "4.3.0 <= v < 5.0.0"
    },
    "elm-version": "0.18.0 <= v < 0.19.0"
}

Anything else that I can do to help with this?

[RobertFischer]

Looks like elm-lang/navigation at 2.1.0 is the problem. I constrained it to 2.0.0 <= v < 2.1.0 and everything compiled fine.

[ericgj]

Do you need Bogdanp/elm-route if you are using evancz/url-parser ? I think they both define an infix </>, which is not currently allowed, and is the source of this obscure message I think.

[evancz]

No reply from OP, so will close. Seems like an elm-package thing anyway though.