web: Migrate WASM initialization to use module_or_path parameter

[ukuq]

The legacy WASM initialization API now triggers a console warning:

"using deprecated parameters for the initialization function; pass a single object instead"

So migrate to the new one

// Before (deprecated):
wasm_bindgen(your_array_buffer); 

// After (recommended):
wasm_bindgen({ module_or_path: your_array_buffer });

[torokati44]

This seems legit, thank you!
rustwasm/wasm-bindgen#3995 (comment)

I just don't like the PR title / commit message.
The change itself LGTM, but please squash on merge, with a proper (tagged and capitalized) commit message!

[ukuq]

This seems legit, thank you! rustwasm/wasm-bindgen#3995 (comment)

I just don't like the PR title / commit message. The change itself LGTM, but please squash on merge, with a proper (tagged and capitalized) commit message!

I'm new to this. Thanks for your guidance

[danielhjacobs]

I'm new to this.

You're also going to have some issues if you try to pull into your master branch the current content of the upstream master branch, which you'll want to do if you want to make another change in the future. For future reference, it will make things significantly easier for you in the long run to create a new branch on your fork using the master branch as a base and make a pull request using that branch.