Skip to content

Not able to get passed piping string into javascript #43

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

Closed
PrismaPhonic opened this issue Jan 9, 2019 · 5 comments
Closed

Not able to get passed piping string into javascript #43

PrismaPhonic opened this issue Jan 9, 2019 · 5 comments

Comments

@PrismaPhonic
Copy link

Hi, I've gotten towards the end of section 4 in chapter 4 of the tutorial - the end of 'Rendering with Javascript'. The problem is that I only get the initial render, but it doesn't seem that I get any animation at all. I get an error in the console that links to some of the web assembly (and I can't personally understand the raw web assembly). The console error (Javascript) I keep getting is: RuntimeError: unreachable executed. Any help?

@PrismaPhonic
Copy link
Author

Actually, might be webpack related as I sometimes see this error right before it onn some refreshes: webpack/webpack-dev-server#851

@PrismaPhonic
Copy link
Author

PrismaPhonic commented Jan 9, 2019

Actually, I downgraded my webpack to see if that was it and no dice. Have no idea why I can't seem to get this working at all. It only renders the first frame and then I get a "RuntimeError: unreachable executed" error and no sense of how to fix this. I followed the guide exactly and triple checked all of my code. On a linux system if that makes a difference

@PrismaPhonic
Copy link
Author

closing this issue - turned out to be a typo I made in the tick function - very facepalm moment over here. Sorry to open this ticket!

@fitzgen
Copy link
Member

fitzgen commented Jan 10, 2019

@PrismaPhonic can you share the exact messages in full from the console? Can you also put your exact version of the tutorial code up on github somewhere so we can try and reproduce the issue? One more thing to check: if you clone this repo, does it work for you?

@fitzgen
Copy link
Member

fitzgen commented Jan 10, 2019

closing this issue - turned out to be a typo I made in the tick function - very facepalm moment over here. Sorry to open this ticket!

er oops missed this message. Glad to hear you figured it out! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants