Andy Wermke

Yeah, maybe we should just revert #198 and publish it as a new major version…

Hi! I suppose you're talking about thread pools. No, there is currently no out-of-the-box solution to this. Do you mean killing the whole worker and spawning a new one if...

Hmm, I'm not even sure threads.js is the right tool for the task you describe. threads.js purpose is to make it easy to run JS/TS code on multiple threads. `child_process.spawn()`...

Hey @jimklo. Looks as if it is trying to fetch the worker bundle from `http://localhost:3000/counter` and I guess it does not exist (at least not at that path). The `Unexpected...

Good points! I am not too sure about today's inner workings of react-scripts, though. Not sure if they still set up Babel – maybe there the ES modules are transpiled...

Great stuff, @danieledler! How about we just add a section about CRA to [the docs](https://threads.js.org/getting-started) and link to your demo repo?

@quangta93 Not sure I can follow. We are using threads.js with Parcel in production, so I am quite sure this works 😉 If you are using Parcel then `threads` will...

@quangta93 Check out the worker path: You try to run `new Worker("./workers/counter")` while the actual worker file seems to be `./worker` – Parcel is choking on that in a weird...

Thanks for bringing this up. yarn pnp is currently not supported. Feel free to share or propose a PR, though, in case you stumble upon a quick fix :)

Yeah, that would be the way to go 👍