bug: `WebAssembly.instantiateStreaming` failed

[georglauterbach]

Steps To Reproduce

I host Bitwarden via the unified deployment myself. When I open the web interface, everything seems to be working as expected, but I get the following warning in the browser console's logs:

wasm loading:16 `WebAssembly.instantiateStreaming` failed because your server does not serve wasm with `application/wasm` MIME type. Falling back to `WebAssembly.instantiate` which is slower. Original error:
 TypeError: Failed to execute 'compile' on 'WebAssembly': Incorrect response MIME type. Expected 'application/wasm'.

(anonymous) @ wasm loading:16
invoke      @ zone.js:369
onInvoke    @ ng_zone.ts:470

Promise.then
invoke      @ zone.js:368
run         @ zone.js:111
(anonymous) @ zone.js:2538

Promise.then
invokeTask   @ zone.js:402
onInvokeTask @ ng_zone.ts:447
invokeTask   @ zone.js:401
runTask      @ zone.js:159
y            @ zone.js:581

Promise.then
d @ zone.js:557
g @ zone.js:568
...

Expected Result

The warning should not be there.

Actual Result

Currently, noting seems to be going wrong, except for a short "freeze" time when I enter the password. Presumably this is because a blocking interface is used instead of the streaming interface? So it would indeed be nice to use the streaming interface.

Screenshots or Videos

Additional Context

No response

Build Version

2025.6.0

Environment

Self-Hosted

Environment Details

• running on Kubernetes via the ghcr.io/bitwarden/self-host:2025.6.2-beta image

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.