-
Notifications
You must be signed in to change notification settings - Fork 63
"_U.list is not a function" When debugging with elm 0.16 #156
Comments
Are you sure that in addition to updating to 0.16, your |
I thought that ELM_HOME wasn't needed for 0.16 (or at least that was the idea). having to check and set it every time is a downer =( Anyways changed it to |
I'm also seeing a fatal "not a function" error in javascript console when using the 0.16 elm reactor in debug mode. I don't have ELM_HOME set. Running in Mac OS X with 0.16 installed from package. |
Seems to be happening at debug.js:9560:26. Elm.Native.Slider.make = function(localRuntime) { |
@fredcy I think you should try setting it. take a look at #131 (comment) |
I tried with ELM_HOME set (to /usr/local/share/elm) and I get the same error as before. |
@jvoigtlaender bummer =( Would uploading my code to a repo help you help me solving this error? |
I'm not really an expert in |
Looks like a semi-colon is missing at debug.js:9637, the end of the Elm.Native.Slider.make function. |
@fredcy looks fine to me
|
If I patch debug.js to add that semicolon I get past the fatal "not a function" error. But then I get an error about "up.props is undefined" appearing in the right pane of the reactor window. That's happening in the customButton() function. https://github.com/elm-lang/core/issues/438 |
@evancz, it seems |
I have the same error, installed 0.16 from npm on linux |
Same problem with 0.16 on Mac OS X |
It looks like someone also has the problem with http://elm-lang.org/try: https://www.reddit.com/r/elm/comments/3tg8es/016_compiler_problem/ |
There is a new version of elm-reactor that is a ton better, so I am just going to focus on getting that ready real quick. There may be a week or two in the meantime, but if you are able to start tracking down the root issues here please do a PR and @ mention me. |
@evancz what are the new features and/or improvements in the new version of the elm-reactor? |
@flip111, why is that relevant at this point? Isn't it more useful to get it fixed and released as soon as possible (then with a blog post advertising the improvements) than taking time now to detail the improvements here and now, for a limited audience? |
it's not relevant, i was just curious ... perhaps there is a list somewhere already |
There are for sure discussions (and, if I remember correctly, mock ups of the UI) on one of the mailing lists. |
This addresses the immediate symptom reported in elm-lang#157 and potentially in elm-lang#156.
So the root here was that ELM_HOME is still needed? If so, let's close it. This is going to be fixed in the next release of the platform, it cannot be done as a patch. |
it was the missing semicolon that 6db89d0 solved, so we can close this =) |
Cool, thanks for the report and for letting us know what happened in the end! |
I still have this problem. |
@milanvdm, still? Have you re-installed 0.16 and the |
Updated to 0.16 and now I'm getting this error when debugging, I think it's a runtime error and not a compile time one. Non debugging compiles and runs fine.
The text was updated successfully, but these errors were encountered: