-
-
Notifications
You must be signed in to change notification settings - Fork 697
Browsers without WebAssembly support not working - workarounds? #3397
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
Comments
Thanks for creating issue. |
Many heart and thank you emojis |
@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! |
Uh oh!
There was an error while loading. Please reload this page.
Environment
π« Firefox ESR 138.0.3 (64-bit) Linux
π« Vanadium 137.0.7151.72
β Firefox 138.0.3 (aarch64) macOS
β 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
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
The text was updated successfully, but these errors were encountered: