Reducing wasm binary size

[ChrisB9]

Hi,
I built a survey with dioxus-web and the wasm binary currently is at staggering 65mb...
I found this issue here: #732 and while I havent tried it out yet, I dont think I will gain massive amount of improvements, as 30mb for a binary still feels quite large.

Has anyone more tips on how to improve binary size?
I think the first thing I could do would be to replace serde with something smaller?

---

fyi - these are my depencencies:

dioxus = "0.3"
dioxus-logger = "0.4.1"
dioxus-web = "^0.3.2"
log = "0.4.17"
reqwest = { version = "0.11.16", features = ["json", "serde_json"]}
serde = { version = "1.0.160", features = ["derive"] }
serde_json = "1.0.96"
once_cell = "1.10.0"
rust-i18n = "1"
dioxus-router = "0.3.0"
web-sys = { version = "0.3.61", features = ["Window", "WindowClient"]}
fluvio-wasm-timer = "0.2.5"
timer-kit = { version = "0.1.1", features = ["fluvio-wasm-timer"]}

[ChrisB9]

I feel really stupid.. for everyone in the future to stumble across this:
check if you ran your build command in a debug-mode.
I realized this, as I ran my binary against twiggy. Now its 900kb big (It is not small, but significantly better than what I had before)

[ealmloff]

Serde can definitely make a large difference in size especially if you derive serialization for many types. The best thing to do is test your binary with twiggy to see where the bloat is coming from.

But there are some general things that can help a lot:

1. Build release builds with trunk (with wasm-opt)
2. Set the opt-size to s or z to optimize for size

[ChrisB9]

The latter option is set, and yes thanks to twiggy I realized my own stupidity.
So you recommend using trunk over dioxus build?

[ealmloff]

For release builds trunk will produce smaller binaries. For debug builds, dioxus supports rsx hot reloading. Dioxus currently does not integrate with wasm-opt but there is a PR open to fix this: DioxusLabs/cli#124. WASM opt makes a huge difference in binary sizes

[ChrisB9]

Thank you, that slashed another 100kb off of my binary without changing any code, that's pretty impressive!
I am generally impressed by dioxus, really amazing work!
My first wasm app is now running in production and it's so far very smooth and I haven't heard any complaints so far. How do you handle errors happening in production, since things like sentry don't work in that environment?