Skip to content
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

[Error]: WebAssembly issue. #605

Open
MarketingPip opened this issue Nov 22, 2023 · 5 comments
Open

[Error]: WebAssembly issue. #605

MarketingPip opened this issue Nov 22, 2023 · 5 comments

Comments

@MarketingPip
Copy link

Can not seem to get things working - do not know if my environment etc? (inside iframe & can not set package.json)

"Aborted(both async and sync fetching of the wasm failed)"
"failed to asynchronously prepare wasm: RuntimeError: Aborted(both async and sync fetching of the wasm failed). Build with -sASSERTIONS for more info."
"Aborted(RuntimeError: Aborted(both async and sync fetching of the wasm failed). Build with -sASSERTIONS for more info.)"

Would be great for proper example of usage via import in browser plus proper build to use.

@verhovsky
Copy link
Member

verhovsky commented Nov 22, 2023

Look at the webpack.config.json file for curlconverter.com:

https://github.com/curlconverter/curlconverter.github.io/blob/master/webpack.config.js

@MarketingPip
Copy link
Author

@verhovsky - can I suggest that if not imported etc you look for these via script tag in window (if window is defined). Then throw error if not found. (in window & in node modules).

Tho when using the "built" version from "esm.sh" - this error still throws. (Which in the online build - it should also be automatically imported / added to the build).

@MarketingPip
Copy link
Author

@verhovsky - just looking over. What about possibly using as dynamic import in browser if not in window? Then if in window use a basic typeof check to validate its the proper WASM files needed?

(just a thought)

@verhovsky
Copy link
Member

I don't understand what you're suggesting.

@MarketingPip
Copy link
Author

@verhovsky when using a build from say ESM.sh (cdn). These will / were not resolving properly.

As well - possibly a variable / way to DEFINE the path you want to use for WASM might be ideal. 👌

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

No branches or pull requests

2 participants