Re: [elm-discuss] Wrong package not found reported using elm-make 0.18.0

Yeah, it can be hard to figure out where in the tool-chain a bug is happening. I usually wind up searching the issue trackers for all of the elm-lang projects, just to be safe :-) On Fri, Mar 3, 2017 at 2:05 PM, hossameldeenfci wrote: > Thank you. Found it strange that no-one faced it in elm-mak

Re: [elm-discuss] Wrong package not found reported using elm-make 0.18.0

Thank you. Found it strange that no-one faced it in elm-make issues :) On Friday, March 3, 2017 at 11:50:27 PM UTC+2, Nick H wrote: > > This is a nice detailed description of the bug! I see this behavior too. > > BUT this is not an issue with elm-make. It is an issue with elm-package. > And there

Re: [elm-discuss] Wrong package not found reported using elm-make 0.18.0

This is a nice detailed description of the bug! I see this behavior too. BUT this is not an issue with elm-make. It is an issue with elm-package. And there is already a bug report open there . (elm-make is running elm-package silently, and it is

[elm-discuss] Wrong package not found reported using elm-make 0.18.0

The purpose of this post is for someone to double-check on me before I post an issue to elm-make . *Summary* When a *non-existent package version* is specified (let's call the package *Foo*), instead of *elm-make* saying the error is with package Foo, it say