Closed jackw closed 3 weeks ago
Interestingly I see zero difference in the generated module.js when using experiments.asyncWebAssembly
vs asset/resource
:shrug:
Given that the asyncWebAssembly
flag will default to true
in the next version of Webpack it feels like it might be the better call, as there may be future WASM-based optimizations built in to Webpack.
:rocket: Issue was released in @grafana/create-plugin@4.12.0
:rocket:
Which areas does this feature request relate to
Problem
Machine learning related projects/libraries can contain wasm files that the current webpack config doesn't know how to handle. Rather than expect plugin developers to customise their configs for these libraries it's probably better that we support it out the box.
Solution
Update the config to support wasm. Webpack has multiple options here:
experiments.asyncWebAssembly
.asset/resource
.Alternatives
No response
Additional context
No response
Are you interested in contributing the solution?