Changes in the way browsers work with wasm causes issues with some js implementation to load the wasm.

[Jieiku]

I am wrapping up a refactor on Abridge.

I needed to test that tinysearch still works, and I ran into an error I have not seen before:

I then see its also an issue on endler.dev just click into the search box with the developer console open and you will see it:

So I then tried the endler.dev demo file and it is working properly, so it seems the actual wasm is OK? but the way that we load it in JS is the problem?

I am not yet sure what to do to fix it. It seems its related to loading the wasm on demand, when a user clicks into the search box, ideally we want to keep the ability to do that.

[mre]

Similar problem here: rustwasm/wasm-bindgen#2779

Thanks for reporting.

[mre]

We should check with the latest wasm-pack version and double-check if we use release mode everywhere.

[Jieiku]

I tested using tinysearch v7 as well. no difference. (that one definitely used to work) I don't have time to check anything else today, headed to work shortly.

[mre]

Appreciate the feedback. 👍