feat(checkout): create new method to register extension web worker

[richapatel1510]

What?

Create new method to register extension web worker

Why?

Support building checkout extension using web worker.

Testing / Proof

• CI checks

@bigcommerce/team-checkout

[bc-peng]

LGTM👏👏

[animesh1987]

Can we type this as an enum, and then we can use the value here https://github.com/bigcommerce/checkout-sdk-js/pull/2869/files extension-action-creator.

[richapatel1510]

Sure, will do that in my next open PR #2876

[animesh1987]

Can I ask what this does?

[animesh1987]

@davidchin can you please take a look at this as well.

On a quick search on internet I can see this as a thing as well

fetch('https://test.com/script.js')
  .then((response) => response.text())
  .then((code) => {
    const blob = new Blob([code], { type: 'application/javascript' });
    const url = URL.createObjectURL(blob);
    const worker = new Worker(url);

    worker.onmessage = (e) => {
      console.log('Worker says:', e.data);
    };

    worker.postMessage('Hello from main thread');

    // Optional: revoke the URL when done
    // URL.revokeObjectURL(url);
  });

[richapatel1510]

This is mainly because we are creating a web worker from a script url that is not on our origin, due to which we get a CORS error when we try to create worker directly by doing new Worker(new URL(url)).

Ref: https://github.com/jantimon/remote-web-worker/blob/main/src/index.ts

Related threads: https://stackoverflow.com/questions/21913673/execute-web-worker-from-different-origin/62914052#62914052
https://stackoverflow.com/questions/58098143/why-are-cross-origin-workers-blocked-and-why-is-the-workaround-ok/60015898#60015898