Jason Miller

Breaking request/response unfortunately makes task chaining impossible. We (will) have [Transferable Streams](https://github.com/whatwg/streams/blob/master/transferable-streams-explainer.md) soon, but the use-cases for this are probably better-suited to a typical Dedicated Worker. Thinking about pooling mainly...

Yup, that's what `workerize-loader` is for. Alternatively, it would be pretty easy to add `{ type: 'module' }` to the Worker instance here, which would enable ES Module imports in...

Using ES Modules is now supported in [0.1.5](https://github.com/developit/workerize/releases/tag/0.1.5). It works like this: ```js import workerize from 'workerize'; const worker = workerize(` import fetchJson from './fetcher' export function get(url) { return...

You need to use a browser that supports modules-in-Workers. I believe Chrome Canary would let you try that out.

heh - `i` was a mistake, but it still worked for automatic methods because it was using `i` from the outer scope. `call` and `expose` are both exposed because sometimes...

terminate() should work.

I haven't had a chance to dig into it yet, but my guess is that this happens due to your bundler ending up choosing the browser version of Comlink rather...

You need to import those polyfills in both your main thread code and your worker.

I think right now there isn't really an interaction between the two. The polyfill would allow WASM as it is implemented using Workers for the threadpool, however the proposal (publishing...

@chicoxyzzy you're right, I'm not sure why I implied WASM couldn't be used - there's no reason it can't here. ```js const wasm = WebAssembly.instantiateStreaming(fetch('worklet.wasm')); class WasmDemoProcessor { async process(data)...