BitBox WASM - planned move to webpack 5 or use wasm-loader with webpack 4?

[Tomasvrba]

Previous (bitbox02-api) is being deprecated.
The new one is much smaller in size, comes with complete TypeScript, and is a proper ES6 module and is based on WASM
I am currently working on switching the dependency in MEW

for this it would be ideal to have webpack v5 to enable experimental features:

experiments: {
    asyncWebAssembly: true
}

There is a way to do this with webpack 4, but it's slightly more complicated so I am wondering which way you'd prefer to do it?
Are you planning or open to moving to webpack 5 or should I do this in webpack 4?

Thanks!

[gamalielhere]

@Tomasvrba I'm currently working on migrating to webpack 5 but it's been tricky to do so at the moment as it causes a bunch of failures. Work has been started here #4778 but that may be preceded in the near future. If you can, do it on webpack 4 for now

[Tomasvrba]

@gamalielhere do you have any guess at all for when webpack 5 might be ready?
Spent a few hours trying to get the wasm module to work with webpack 4, but could not get it to work