Maintenance of the webpack loader about comlink HOT 7 CLOSED

Apologies for the radio silence. I would indeed recommend going with worker-plugin + comlink. It's a little less magic and avoids the tradeoffs comlink-loader comes with.

from comlink.

@surma I have resorted to using webpack's worker loader and comlink. The combination works very well and hopefully, that is the recommendation going forward instead of using the comlink webpack loader.

from comlink.

@JesseFarebro could you point us out to a working demo of the implementation? I keep running into random issues... :(

from comlink.

I didn’t write comlink-loader, @developit did.

That being said, I think it’s saner to deprecate comlink-loader and point to the much more generic worker-plugin. It should make workers with webpack work like a charm.

@developit WDYT?

from comlink.

Can Comlink be used in conjunction with worker-plugin? It seems like they are entirely different things. worker-plugin seems to just loads workers where as Comlink actually proxies things and makes working with workers easy. Am I missing something?

from comlink.

You are right, they solving completely different problems — but that is a sign that they are work well together, no?

worker-plugin teaches webpack to understand the Worker constructor. You don’t need to create a separate entry point or anything in your webpack config to make that work. But it just gives you a normal worker instance.

Comlink can be used on top of that to give you the ergonomics.

We are using this very combination in Squoosh.

from comlink.

Going to close this as it doesn’t seem actionable anymore.

Please re-open if you disagree.

from comlink.