Hi Janis,
yes, this seems to be related. I created an SSCCE to the best of my
abilities: https://github.com/RobertWalter83/sscce-elm-ports-uncaughtError
Check out the readme if you are interested.
Will post a comment to the isse you pointed me to.
On Monday, August 8, 2016 at 8:14:30 PM UTC+2,
@robert: are you using webpack loader? We tracked this bug to an
elm-webpack-loader behaviour. here is the
issue. https://github.com/rtfeldman/elm-webpack-loader/issues/60
For now, the workaround I am using is to import Json.Decode in my Ports
file.
On Monday, 8 August 2016 22:30:16 UTC+5:30,
@Robert, maybe yours is a new bug, that was introduced with core version
4.0.3 or 4.0.4 (released just a few days ago)? See
https://github.com/elm-lang/core/issues/683.
2016-08-08 19:00 GMT+02:00 Robert Walter :
> It doesn't seem like it is tracked. I ran into the
It doesn't seem like it is tracked. I ran into the same(?) issue in my
project and I tried to create a SSCCE so I could file an issue, but the
thing is I cannot get a SSCCE to fail like my project. My projec tis in the
middle of a bigger refactoring, which makes it particularly hard for me to
Cool bug find :) Is it tracked on
https://github.com/elm-lang/elm-compiler/issues ?
On Sun, Jul 31, 2016 at 3:01 AM, Aditya Vishwakarma <
blackleopar...@gmail.com> wrote:
> Hi
>
> So I dug deeper into this issue. turns out that the JS code for my port
> module was being emitted before the JS of
Hi
So I dug deeper into this issue. turns out that the JS code for my port
module was being emitted before the JS of Json.Decode module.
After some research, I found that if the project's port module has:
- Name beginning with a letter before J, and
- does not have a declared dependency