upgrade packages and use threadsjs#43
Conversation
|
I disabled |
|
@3xtr4t3rr3str14l Try this library, it's working great in Lodestar! https://www.npmjs.com/package/threads |
|
@dapplion I tried using threads, and I have most of the code setup, but I'm running into webpack/script loading/etc woes. I've tried a bunch of things, and almost every time I try something I get these errors in the console: Any idea what might be going on? I thought I had all the types right in my webpack config, but now I'm not sure. This wasn't happening when I was using the native web workers, fwiw. |
|
This pull request introduces 1 alert when merging e541661 into 1fc8fb3 - view on LGTM.com new alerts:
|
|
This pull request introduces 1 alert when merging 0e74c7d into 1fc8fb3 - view on LGTM.com new alerts:
|
fixed this. ready for review again |
|
This pull request introduces 1 alert when merging 30980cf into 1fc8fb3 - view on LGTM.com new alerts:
|
|
This pull request introduces 1 alert when merging 10889cd into 1fc8fb3 - view on LGTM.com new alerts:
|
Resolves #41 by upgrading to webpack 5 and using threadsjs for the web workers.
Since we were originally using the web-worker with an inline loader, but are no longer doing so under this PR, I also made a separate entry in the webpack config to transpile the worker
*.tsfile(s) into their ownworker.tsMoving from
workerize-loadersto native web workers also opened the door to upgrade all the other packages in the repo, so I did that as well.Also resolves #40