-
Notifications
You must be signed in to change notification settings - Fork 71
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
Combine .wasm and .js files [3 XMR] #248
Comments
There is a bounty on this issue. The amount is in the title. The reward will be awarded to the first person or group of people who resolve this issue. If you are starting to work on this bounty, please write a comment so that we can assign the issue to you. We expect contributors to provide a PR in a reasonable timeframe or, in case of an extensive work, updates on their progress. We will unassign the issue if we feel the assignee is not responsive or has abandoned the task. Read the full conditions and details of the bounty system. |
Comparing bytesize (see below) of dist compressed and uncompressed artifacts it is clear that compression brings a lot of benefit. Modern webservers do compress the static assets and moder browsers can handle the compressed assets. So the bandwidth consumption will be lower as compared to raw files. Base64 bloats any binary by a max factor of
|
Zipped
|
Resolved with #250, which was incorporated in v0.11.0. |
This issue requests combining the .wasm and .js files, as requested in #83.
#247 succeeds to combine the .wasm and .js files within dist and is tested to work in the browser.
However, monero_web_worker.js swells to 10.4 mbs, and monero_web_worker.js.map is 14.5 mbs. Ideally, the web worker can remain at or below 1.5 mbs and the source map at 5.5 mbs.
If the file sizes increase too much, it may not be worth it.
In addition, the project should be configured to use the combined .js files "as is", without manually copying them to the public folder for web apps.
The text was updated successfully, but these errors were encountered: