Andy Wermke

I just ported the latest changes of `GoogleChromeLabs/worker-plugin` and published it as `threads-plugin` `v1.1.0`. Would be great if you can give it a try - I think it should be...

I just saw that there is a subtle difference to the latest version of the `worker-plugin`: The place where the worker ID counter is declared. Can you quickly try monkey-patching...

Thanks for the link, @bebraw! Looks like we can just port this section [here](https://github.com/prateekbh/babel-esm-plugin/blob/master/src/index.js#L151-L179).

It works with TypeScript, you just need to set `module` to `esnext` as you already wrote. It's also documented like that: See [here](https://github.com/andywer/threads-plugin#typescript). The error above is unrelated to threads.js...

Feel free to re-open if I missed something. The error above looks very much like something else is fishy, though.

Well, if you out-comment the threads-plugin, then webpack won't even know that it should process the worker script and its dependencies, so it won't crash as the worker's code isn't...

Wow, that seems like a weird issue and requires more time to investigate then.

Can you please check if it's fixed in the latest version? #16 might have fixed it.

@raz-sinay Cool, thanks! @jc-lab Can you try and confirm that it works? If so, let's add a `target` option to the `threads-plugin` that defaults to the webpack config's main `target`...

@pverscha Sure, but you shouldn't… 😅 One little XSS vulnerability in your webapp code and the attacker can take over your whole system at once ;) I wouldn't use `fs`...