I think this is highly likely, since they specifically target this usecase - wasm in a browser.
I guess my question is more along the lines of “how can I make that error message more verbose”, to see what actual call triggers the error, so I can focus on that.