See also https://bugs.chromium.org/p/skia/issues/detail?id=10360

Image decoding in Flutter is already asynchronous, so this would be a non-breaking change. There are two ways to move image decoding to web workers:

• Use WASM thread support and use a web-worker as a second thread. It can be used for image decoding without blocking the main UI thread. In the future we can move font decoders there too. Image data can be passed efficiently by sharing WASM memory.
• Use Canvas2D on a web-worker. Image data can be passed efficiently using transferrable arrays.