-
Notifications
You must be signed in to change notification settings - Fork 8
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
fails to load when built to WASM #11
Comments
Seems to be coming from this line which seems to be a known issue with |
I can confirm it works with my fork here where i simply delete that code - I can use that for now since I am not taking advantage of any async code 👍🏻 If you want I can look about adding a flag for async stuff? |
That code should only need to run |
(As a bigger refactor, I was thinking this code could be made into more of a co-routine pattern, meaning the code related to time and milliseconds could be abstracted out. The timing aspect is just a function that says "keep going" or "stop", and it feels weird to have this core function dealing directly in milliseconds.) |
I think that this PR should fix this issue and enables the use of async feature in WASM too: #12 I could not test it. @jaminhaber , could you test it before I merge? @IFcoltransG, what do you think about this solution? |
Yep! I am able to run the game in wasm with this:
|
Branch merged in master. |
I have a bevy project with the story added as a
NonSend
resource but I am encountering the following error when exporting as WASM and embedding on a web page.The error may or may not be related to this package but just wanted to flag it
Main fn:
Error:
The text was updated successfully, but these errors were encountered: