New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Core 4.0.4 Breaks Elm Reactor #688

Closed
Kwarrtz opened this Issue Aug 10, 2016 · 3 comments

Comments

Projects
None yet
3 participants
@Kwarrtz

Kwarrtz commented Aug 10, 2016

After updating from core v4.0.3 to v4.0.4, my programs stopped working in the reactor. The program select screen worked fine, but when I went to run my program, it just displayed a blank screen. Pulling up the element inspector, I found that the body tag was empty and there were two errors on my JS console.

Uncaught ReferenceError: _elm_lang$core$Json_Encode$string is not defined
Uncaught TypeError: runElmProgram is not a function

Reverting to core 4.0.3 fixed the issue.

I am running Elm 0.17.1 on Chrome v54 and Mac OS X Yosemite.

@process-bot

This comment has been minimized.

Show comment
Hide comment
@process-bot

process-bot Aug 10, 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 Aug 10, 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.

@evancz

This comment has been minimized.

Show comment
Hide comment
@evancz

evancz Aug 10, 2016

Member

Can you try deleting the elm-stuff/ directory and trying again? What happens?

Member

evancz commented Aug 10, 2016

Can you try deleting the elm-stuff/ directory and trying again? What happens?

@Kwarrtz

This comment has been minimized.

Show comment
Hide comment
@Kwarrtz

Kwarrtz Aug 10, 2016

Ah! That solved it.

Thank you.

Kwarrtz commented Aug 10, 2016

Ah! That solved it.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment