Andy Wermke

Good point, @kellyselden! As it turns out, it should already be supported, undocumented and untyped, though 😉 `new Worker()` accepts a second, optional `options` argument. It will just be passed...

Great stuff, @rhansen! Thanks so much. @mjgp2 Can you check if this fix solves the issue for you, too? I don't see any reason why not, but an additional test...

Hey @tuturis. Can't really tell as I tried to use the VS code debugger like three times in my life without much success, so I just didn't try again. What...

Thanks, @Dobloq! I see… I am not surprised that it fails with that spawn timeout error (if the debugger halts the new thread immediately, of course it cannot tell the...

Thanks for sharing, @ttessarolo! We should document that somewhere… Feel free to propose a PR.

Hey @brandonros! That's a C++ error. Are you sure `gs-usb` works from within worker threads? Never tried to use a native dependency within a worker thread, tbh.

Any updates?

Hey @ashishchandr70, thanks for reporting! What version of node.js and threads.js are you running?

Looks to me as if the native code in your `grpc` package is not comfortable being run in a worker thread. Forcing the use of tiny-worker instead of worker threads...

> like somehow making the worker_threads module not resolve ? Would be pretty hacky, but making the import from worker_threads throw would probably work if tiny-worker is installed.