zlib-sys to flate 2 with the zlib backend, and for wasm flate 2 with the rust-native backend
https://doc.rust-lang.org/reference/conditional-compilation.html
^ this leads me to believe my dependencies should look smth like this:
[target.'cfg(target_family = "wasm")'.dependencies]
flate2 = { version = "1.0.17", features = ["rust_backend"] }
[target.'cfg(not(target_family = "wasm"))'.dependencies]
flate2 = { version = "1.0.17", features = ["zlib"] }
However, this apparently isn't it yet. However my observations while fiddling around a bit seem so damn contradictive that I wanted to see if you might have an idea:
with the configuration above, both the wasm and non-wasm build use the zlib backend
if I remove the first two lines, the wasm build fails due to flate2 being an undeclared crate or module and the non-wasm build succeeds
If I change the zlib to rust_backend in the bottom two lines both wasm and non-wasm builds use the rust_backend 
05][client/sound]: sound init successful using audio driver 'pipewire'
05][client/sound]: sound init successful using audio driver 'pipewire'
1
4 4
2
gfx_render_thread_count 16 to use as many cores as possible
but that doesnt mean it will max all cores out
