Menci

That will just make my app know there's an error. The browser will show the download as successfully finished.

What I REALLY can't understand is when I click a prefetched link, the `getView()` is called again so the resources are fetched again. So WHAT'S THE MEANING OF THE PREFETCH?

ping @jamesknelson

No, not just beforeunload. If you click "back" or "forward" button in browser's navigation bar, NO EVENT could let you cancel the history pop. On Mon, Dec 7, 2020 at...

Here is a workaround. The filename works on Chrome, but it's non-standard: ```js return await this.minioClient.presignedGetObject( this.configService.config.fileStorage.bucket, uuid, FILE_DOWNLOAD_EXPIRE_TIME, { "response-content-disposition": "attachment; filename=\"" + encodeRFC5987ValueChars(filename) + "\"" } ); ```

Without a function providing the WASM location, the module won't work in Webpack.

Another workaround (without patching web-tree-sitter) is patching the `fetch` function: ```js function patchFetch() { const realFetch = window.fetch; window.fetch = function () { if (arguments[0].endsWith("/tree-sitter.wasm")) arguments[0] = TreeSitterWasmUrl; return realFetch.apply(window,...

No, don't encode the WASM file to the JS file. BASE64 increased the bundle size for nothing.

@drom Yes, the `Parser.init` is called after the emscripten's glue code start trying to load the WASM file. So we need some changes to the structure. #569 does some restructure...

I'm attempting to reproduce it but encountered an error building your Rust code: Could you please test it using my plugin https://www.npmjs.com/package/vite-plugin-wasm and the `bundler` target?