FTR: This is half rant and half a serious request for help.
I’ve been trying to get the wasm-pack tutorial app to load client-side without using the webpack-dev-server. And I’m hitting a brick wall there: the webpack-dev-server works fine, but it works with default settings and getting a feel for what’s necessary to get it into production is an exercise in frustration, and thusfar a fruitless one.
Specifically, all kinds of sources tell me that
wasm modules need to be asynchronously loaded.
But that’s exactly what I don’t want, because:
- It’s a really ugly solution (and yeah I get the perf rationale behind it, but it’s more work than it should be, and ATM I don’t give 2 flying farts about performance. First I need to get it working, then I’ll see about the rest)
- It’s does not necessarily fit nicely into the larger project I need to integrate this project into.
So what do I need? I think I need a webpack config that:
- actually works (all the loaders so far fail miserably in actually getting the job done. I’ve tried
- Allows me to integrate the project into another, larger one that runs in the browser.
In case it matters: the larger project is based on AngularJS (yes, the v1 one. But if it does matter, I can’t imagine that AngularJS is actually helpful here).
Can anyone help a fellow rustacean out?