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 <hossameldeen...@gmail.com> wrote: > 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 is already a bug report open there >> <https://github.com/elm-lang/elm-package/issues/253>. (elm-make is >> running elm-package silently, and it is elm-package that is giving the >> erroneous "Package configured successfully".) >> >> On Fri, Mar 3, 2017 at 12:05 PM, hossameldeenfci <hossame...@gmail.com> >> wrote: >> >>> The purpose of this post is for someone to double-check on me before I >>> post an issue to elm-make <https://github.com/elm-lang/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 says the *error* is with another package *Bar* whose *version* >>> is *correct*. >>> >>> *Simplest elm-package.json that causes the problem:* >>> >>> { >>> "version": "1.0.0", >>> "summary": "My personal website written in Elm", >>> "repository": "https://github.com/user/project.git";, >>> "license": "All Rights Reserved", >>> "source-directories": [ >>> "." >>> ], >>> "exposed-modules": [], >>> "dependencies": { >>> "evancz/url-parser": "2.1.0 <= v < 3.0.0", >>> "evancz/elm-markdown": "3.0.1 <= v < 4.0.0" >>> }, >>> "elm-version": "0.18.0 <= v < 0.19.0" >>> } >>> >>> >>> *Expected:* >>> >>> >>> >>> *Error: Your .elm/packages/ directory may be corrupted. I was led to >>> believe thatevancz/url-parser existed, but I could not find anything when I >>> went to look upthe published versions of this package.* >>> Or some error on `url-parser`'s version. Because the newest version is >>> 2.0.1, no 2.1.0 version exists. >>> >>> *Actual:* >>> Packages configured successfully! >>> Could not find package evancz/elm-markdown. >>> >>> >>> Maybe your elm-stuff/ directory has been corrupted? You can usually fix >>> stuff >>> like this by deleting elm-stuff/ and rebuilding your project. >>> The problems here are: >>> - First, it says `Package configured successfully`. I don't think that's >>> a correct statement since `url-parser:2.1.0` doesn't exist. >>> - The more important part: `elm-markdown`'s versions are configured >>> correctly, the problem is with `url-parser`. >>> >>> *Extra info:* >>> - I'm in some project, my elm-package.json and elm files are inside elm/ >>> - command run: (cd elm && rm -rf elm-stuff && elm-make Main.elm >>> --output=../assets/gen/javascripts/elm-main.js) >>> - npm elm Version: 0.18.0 >>> - OS: Ubuntu. >>> >>> >>> *So, could someone try this out to see if the same behaviour occurs and >>> confirm if they also think this behaviour is faulty, please?* >>> >>> Thanks in advance! >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Elm Discuss" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to elm-discuss...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elm-discuss+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
