Browsers without WebAssembly support not working - workarounds?

[acidjazz]

Environment

:no_entry_sign: Firefox ESR 138.0.3 (64-bit) Linux :no_entry_sign: Vanadium 137.0.7151.72 :white_check_mark: Firefox 138.0.3 (aarch64) macOS :white_check_mark: Chromium 136.0.7103.113 (64-bit) Linux

Version

v3

Reproduction

Try using a content site with any browser that does not have WebAssembly

Description

So I know v3 support for browsers that don't have WebAssembly is not really on the table, but when running into this issue I was curious if there is some sort of way to just force SSR for these cases so that the can still work.

Currently I have hacks in my setup that I'm not proud of like

  if (import.meta.client && !window.WebAssembly) document.location.reload()

I wonder if there's something we can do in middleware or elsewhere to just at least have the site work?

Additional context

No response

Logs

[farnabaz]

Thanks for creating issue. Just dropped small PR which should fix the issue. I appreciate if you check and confirm fix and behavior.

[acidjazz]

Thanks for creating issue. Just dropped small PR which should fix the issue. I appreciate if you check and confirm fix and behavior.

Many heart and thank you emojis

[farnabaz]

@acidjazz Have you got time to test it? You can test using pr release

npm i https://pkg.pr.new/@nuxt/content@3399

[acidjazz]

@acidjazz Have you got time to test it? You can test using pr release

npm i https://pkg.pr.new/@nuxt/content@3399

No but I will soon and report back ASAP!

[acidjazz]

@farnabaz i tried testing this but ran into the queryCollectionWithEvent issue here because @nuxtjs/sitemap uses this here

[farnabaz]

@acidjazz I'm planning to include this in next release, can you confirm the fix?

[acidjazz]

@farnabaz swamped but will try to find some time today or tomorrow!