Jason Miller

Hi there, In order to figure this one out I'm going to need your Node and Webpack versions, as well as the snippet of code you're using to instantiate the...

Plugin application in child compilers is handled by Webpack, there aren't great defaults since plugins can do anything they want. As an example, it would be logical to copy a...

If anyone has a way to reproduce the supposed circular dependency issue that would be potentially useful. This plugin doesn't modify Webpack's handling of dependencies at all, so if the...

Shouldn't this already work just by adding `SplitChunksPlugin`? We're adding `WebWorkerTemplate`, which generates chunks and a runtime that use `importScripts` or `XHR+eval` for code loading. *Update:* I can confirm that...

What version of Webpack is this? The plugin only supports version 4. My guess is you're on 3 or 5.

If anyone can provide a bit more information here that would be useful. Since this is a version incompatibility, screenshots aren't enough to figure out where the problem lies.

I believe this may be fixed by [5.0.0](https://github.com/GoogleChromeLabs/worker-plugin/releases/tag/5.0.0)?

That's a great idea! It's definitely an option. I wonder if there's a larger question here of "script entry points" - *Worklet `addModule()` would be another that would fit nicely...

yup yup.

Hiya! I'm not sure I follow - would this be different from Greenlet's current support for calling arguments? ```js const foo = greenlet((a, b, c) => [a, b, c]); await...