Uncaught (in promise) LinkError: import object field '__wbg_error_09919627ac0992f5' is not a Function + JsValue(undefined) instead of objects

[Niedzwiedzw]

that happens when I import a package generated by wasm-pack

[Niedzwiedzw]

https://github.com/nshen/vite-plugin-wasm-pack this partially solved it

[Niedzwiedzw]

now the problem is that despite me passing an object into a function, what goes into wasm is read as null.
invalid type: null, expected struct ScheduleImportConfigV2 at line 1 column 4

[Niedzwiedzw]

yeah so I've triple checked it with console.log(myInput) on javascript side just beforre passing that into a wasm function

console.log(myInput) // {a: 1, b: 2}
myWasmPackage.handle_my_input(myInput)

and in rust it's

#[wasm_bindgen(skip_typescript)]
pub fn handle_my_input(my_data: JsValue) -> JsResult<JsValue> {
    console_log!(
        "handle_my_input :: {:#?}",
        my_data
    );
    // ...

}

and it prints

handle_my_input :: JsValue(undefined)

[Niedzwiedzw]

https://github.com/Niedzwiedzw/vite-wasm-pack-error-showcase here's a repository showcasing this problem

[Menci]

I'm attempting to reproduce it but encountered an error building your Rust code:

Could you please test it using my plugin https://www.npmjs.com/package/vite-plugin-wasm and the bundler target?

[Jieiku]

I ran into this Q4 2023 but was unable to figure out the cause, and because of that I quit using tinysearch.

I opened the issue here: tinysearch/tinysearch#175

I setup a reproducible test case repo for this here: https://github.com/Jieiku/abridge-tinysearch-dev

The readme in that test case repo has instructions for reproducing this error, I am stumped as to what to do next because I have almost zero rust experience.

If you follow the steps in the readme from the test case repo, here is the result you see in the firefox developer console:

If you do not want to use zola serve, you can alternatively use zola build and upload the files from the public directory to your web server of choice.

[Jieiku]

Should I have opened a new issue? This still happens to me and I see this was moved to discussion.