co-web-worker
Advanced tools
If a site is on domain https://abc.com and wants to run a web worker located at https://xyz.com/dist/worker.js, it won't work.
Cross-origin web workers are not allowed.
So what can be done to get a worker at xyz.com run on abc.com?
Say no more.
$ npm i co-web-worker
import CrossOriginWorker from 'co-web-worker';
console.log(window.location.origin);
// > https://abc.com
const worker = new CrossOriginWorker('https://xyz.com/dist/worker.js');
console.log(worker instanceof Worker);
// > true
Licensed under MIT license. See LICENSE at root of this repo for more information.
FAQs
Cross-origin Web Workers
The npm package co-web-worker receives a total of 2 weekly downloads. As such, co-web-worker popularity was classified as not popular.
We found that co-web-worker demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.