Andy Wermke

@FoxelFox @eranimo This happens only after upgrading to webpack 5 and you are using threads-plugin v1.4.0? If so, can you try going back to webpack 4 for a moment, but...

You don't need the threads-plugin at all with webpack 5 (see #37). Will update the docs accordingly! Nevertheless, thanks for sharing your findings here 👍

Hey @raz-sinay! Sorry, but I don't have a good solution either… You could try removing the `new NodeTargetPlugin()`, as the threads-plugin should apply the NodeTargetPlugin automatically to the webpack child...

I am not sure what the current status is, but we have always used threads.js with the threads-plugin with TypeScript and never saw that error. Might be specific to Electron,...

Yeah, that damn webpack child compiler once more… You could try to monkey-patch a fix here and see if it works: https://github.com/andywer/threads-plugin/blob/master/src/loader.js#L42 Add `loaders` to `workerOptions`, set it to `compilerOptions.loaders`....

Hey Carlos! Can you share the actual code with the `spawn()` invocation?

Thanks for sharing, but you literally sent me everything that could be interesting except the bit that I asked for 🙈😅 > Can you share the actual code with the...

Ahhh, sorry man – my bad! Was a bit in a hurry when I responded to the first comment and didn't notice the snippet at the bottom... So, I don't...

Hey @carlosvillu. Sorry, I've been swamped with work! This is a tricky one. I am not even sure that anything's wrong with the `threads-plugin` as there is in fact an...

Hey @barretron! I am terribly sorry, I just saw your issue. For some reason I wasn't automatically watching the repository... Is that still an issue or did you give up...