Wasm - "unhandled promise rejection" after deployment #2931
-
After deploying my app to production (using a containerfile as recommended in the docs) there is no interactivity. The javascript console in Chrome reports
Here is the relevant section in the project index file. (The project is called leptos-dash)
The code generated in the version run locally that works seems to me to be identical
Safari reports the same error. Everything works fine on my development machine (in both development and release modes) but I have had this error appear and disappear with a clean build. However, my container file builds things from scratch. Any hints on how to go about tracking down where this error comes from? I'm using Axum as the underlying framework. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
I would say that this kind of error is typically a caching issue, related to a version of the JS file and/or the WASM file being served that is not the latest. |
Beta Was this translation helpful? Give feedback.
I would say that this kind of error is typically a caching issue, related to a version of the JS file and/or the WASM file being served that is not the latest.