andywer/threads.js

Confusion with Node.js native Worker

Aperta

#315 aperta il 6 nov 2020

 (4 commenti) (0 reazioni) (0 assegnatari)TypeScript (173 fork)github user discovery
enhancementhelp wanted

Metriche repository

Star
 (3531 stelle)
Metriche merge PR
 (Nessuna PR mergiata in 30 g)

Descrizione

I'm using the threads-plugin for webpack.

I'm creating a new worker the normal way: new ThreadManager(new Worker('path/to/worker'), 2)

But keep getting the 404 error. I tried everything to fix it, can't understand why it's doing it. Until I realize that I didn't add this line: import { Worker } from 'threads'

This has already happened multiple times. Is there anything Threads.js can do to prevent this from happening again? I'm sure others are having the same problem.

Better error messages in general would also be nice. Now they almost always end up as a 404 error with 10 seconds later a timeout. I understand that this might not be the easiest thing with webpack and all. But I'm quite sure a lot of new users run into these unhelpful errors and debugging this can be really hard.

Guida contributor