-
-
Notifications
You must be signed in to change notification settings - Fork 670
Can No Longer Export an Export that Exports from Another File #248
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
Comments
That correct? :) |
Yes exactly :) If you have trouble reproducing let me know, as I may have renamed some exports, using |
Rad, thanks! I'll update wasmboy with this 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello! It has been a while haha! 😄
So after going through and realizing this issue: torch2424/wasmboy#135
I got to catch up on a whole lot of AssemblyScript! 😄 So I went through and made the few updates I needed, and realized not all my functions were correctly exporting.
For instance, see this:
Wasmboy Core, index.ts that exports all of our wasminstance exports:
https://github.com/torch2424/wasmBoy/blob/943d79c3cbf525c00a3d73aa2a26a27b7cb24342/core/index.ts
Another file within the core, that exports a function from another file:
https://github.com/torch2424/wasmBoy/blob/943d79c3cbf525c00a3d73aa2a26a27b7cb24342/core/joypad/index.ts
I found that the Wasm instance exports, e.g
wasmInstance.exports.myExportFunctionHere
were not available. Meaning, I can no longer export functions from a file, that export a function from another file.It was a quick an easy fix for me, but figured I might as well make an issue. Also, my apologies for the confusing title, it was the only thing I could think of, and gave me a good laugh. Thanks!
The text was updated successfully, but these errors were encountered: