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

eversdk.wasm bandwidth consumption #561

Open
shravanandoria opened this issue Oct 20, 2023 · 0 comments
Open

eversdk.wasm bandwidth consumption #561

shravanandoria opened this issue Oct 20, 2023 · 0 comments

Comments

@shravanandoria
Copy link

I've placed eversdk.wasm in my next.js public folder which loads everytime my app renders which results in high bandwidth consumption. I've followed this step for setting up eversdk in next.js (https://github.com/tonlabs/sdk-samples/tree/master/core-examples/next-js/normal-transfer#2-handling-the-wasm-file).

Is is possible to host this eversdk.wasm file somewhere else and then pass it's link in the app or any other possible solution instead of saving the wasm file itself in public folder?

image

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

1 participant