|
|
|
|
|
by the8472
4019 days ago
|
|
Not sure if the security model allows it, but maybe you could write the wasm into a blob, create an URI from the blob[1] and then use that as <script> src. Or maybe data uris. > How does this affect those of us using Babel or TypeScript to output ES3 code? Well, if you're already transpiling the whole load of ES6 features then it's just one more shim to consider, no? [1] https://developer.mozilla.org/en-US/docs/Web/API/URL/createO... |
|
Doing something similar for Workers, one of the problems we've had is that IE and I think Safari block that, so to make it work we have to fall back on a permanently cached shim that puts an eval statement inside self.onmessage. (Obviously no equivalent to eval exists for wasm, or I wouldn't have a problem here in the first place.)