-
Notifications
You must be signed in to change notification settings - Fork 152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Deno Compatibility #486
Comments
Thanks :) A worker is always a separate script: https://github.com/josdejong/workerpool/blob/master/src/WorkerHandler.js#L66 maybe Deno doesn't like that? |
What resolve this issue is using a I did a quick test and the tests do pass if we use a Would it be possible to provide your testing environment? |
yes sure. this is my testing environment
Using a |
It will likely depend on how you obtain the Blob. I don't think using In fact, there's an open issue in Deno about supporting the import of binary or text files: Unlike npm, which imports everything from the remote package into your repository, Deno only downloads the files that are explicitly imported in the package's JavaScript code. Currently, Deno supports importing only JSON files in addition to JS and TS files. |
This is true, Deno also only supports
It also may be possible to use a |
Actually, this is correct. It's their recommended approach, and I tested it both directly and by running it from another package. It appears to work properly in Deno. |
It may be best to use Blob for consistency as we already wrap in cases where we load the |
First of all, I want to say this library is amazing!
Since Deno supports the Web Worker API, I attempted to initialize the pool with the web worker type to configure Deno's permissions accordingly. However, when I try to run it, I encounter the following error (see the image below):
The text was updated successfully, but these errors were encountered: