Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upUndefined errors in 4.0.2 #660
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
process-bot
Jul 13, 2016
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.
process-bot
commented
Jul 13, 2016
|
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. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evancz
Jul 13, 2016
Member
Can you share an http://sscce.org/ and information about your setup?
These problems seem bad, but I can't solve them with the current info. Please open a new issue with that information!
|
Can you share an http://sscce.org/ and information about your setup? These problems seem bad, but I can't solve them with the current info. Please open a new issue with that information! |
evancz
closed this
Jul 13, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
kevinbgreene
Jul 13, 2016
I was setting up a minimum project to share and show the issue and couldn't reproduce. Found deleting elm-stuff and doing a clean elm package install fixed the issue.
kevinbgreene
commented
Jul 13, 2016
|
I was setting up a minimum project to share and show the issue and couldn't reproduce. Found deleting elm-stuff and doing a clean elm package install fixed the issue. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
evancz
Jul 13, 2016
Member
Ah, interesting. That may be some sort of caching bug with elm-make that happens in particular upgrade scenarios. There are some known issues on elm-make about mistakenly trusting the cache, so I'd expect a comprehensive fix there to cover this.
Anyway, thanks for the follow up!
|
Ah, interesting. That may be some sort of caching bug with Anyway, thanks for the follow up! |
kevinbgreene commentedJul 13, 2016
•
edited
Edited 1 time
-
kevinbgreene
edited Jul 13, 2016 (most recent)
After installing 4.0.2 over 4.0.1 I started getting a series of undefined errors in the compiled JavaScript.
The first error was:
This is a just started app. It's only one file and a few lines of code. I am not using Task. However, if I import Task this error goes away and I get another:
Pinning to 4.0.1 solves my issues.