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

Upgrade from elm core 4.0.2 to 4.0.4 breaks Ports #683

Closed
cscalfani opened this Issue Aug 8, 2016 · 4 comments

Comments

Projects
None yet
3 participants
@cscalfani

cscalfani commented Aug 8, 2016

I now need to import Json.Decode and Json.Encode for my port module. If omitted, the compiler doesn't produce an error. Instead I get the dreaded Runtime Error:

ReferenceError: _elm_lang$core$Json_Decode$string is not defined

@process-bot

This comment has been minimized.

Show comment
Hide comment
@process-bot

process-bot Aug 8, 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 8, 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
Member

evancz commented Aug 8, 2016

Include an http://sscce.org/

@cscalfani

This comment has been minimized.

Show comment
Hide comment
@cscalfani

cscalfani Aug 8, 2016

Okay, so I realized that the problem had to do with how I was building the app. Not sure why an upgrade to 4.0.4 changed the behavior that was working just fine all last week. Don't really care because I've changed my build process.

Sorry for the false alarm.

cscalfani commented Aug 8, 2016

Okay, so I realized that the problem had to do with how I was building the app. Not sure why an upgrade to 4.0.4 changed the behavior that was working just fine all last week. Don't really care because I've changed my build process.

Sorry for the false alarm.

@cscalfani cscalfani closed this Aug 8, 2016

@evancz

This comment has been minimized.

Show comment
Hide comment
@evancz

evancz Aug 8, 2016

Member

No worries, glad it is working again!

(It may have been about assets getting stuck in elm-stuff/build-artifacts/ which will get fixed via some elm-make improvements.)

Member

evancz commented Aug 8, 2016

No worries, glad it is working again!

(It may have been about assets getting stuck in elm-stuff/build-artifacts/ which will get fixed via some elm-make improvements.)

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