Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Use WebAssembly to speed up SourceMapConsumer #306
This is big enough and covers enough different things that it is going to suffer from the other side of bikeshedding -- that is, I tried to read it all but I'm not sure I can really do it justice.
I do wonder if it's possible to remove the need for a separate wasm URL and thus (IIUC) the need for the constructor to return a promise.
Compiling wasm is still done off-thread, and returns a promise, so even if we already had the blob, the constructor would still return a promise.
referenced this pull request
Jan 18, 2018
FYI, https://hacks.mozilla.org/2018/01/oxidizing-source-maps-with-rust-and-webassembly/ is live with details on the experience.
Going to go ahead and merge this PR!