The postMessage() method of the DedicatedWorkerGlobalScope interface sends a message to the main thread that spawned it.
This accepts a data parameter, which contains data to copy from the worker to the main thread. The data may be any value or JavaScript object handled by the structured clone algorithm, which includes cyclical references.
The method also accepts an optional array of transferable objects to transfer to the main thread; Unlike the data parameter transferred objects are no longer usable in the worker thread. (Where possible, objects are transferred using a high performance zero-copy operation).
The main scope that spawned the worker can send back information to the thread that spawned it using the Worker.postMessage method.
postMessage(message)
postMessage(message, options)
postMessage(message, transfer)
The following code snippet shows worker.js, in which an onmessage handler is used to handle messages from the main script. Inside the handler a calculation is done from which a result message is created; this is then sent back to the main thread using postMessage(workerResult);
onmessage = (e) => {
console.log("Message received from main script");
const workerResult = `Result: ${e.data[0] * e.data[1]}`;
console.log("Posting message back to main script");
postMessage(workerResult);
};
In the main script, onmessage would have to be called on a Worker object, whereas inside the worker script you just need onmessage because the worker is effectively the global scope (DedicatedWorkerGlobalScope).
For a full example, see our Basic dedicated worker example (run dedicated worker).
Note: postMessage() can only send a single object at once. As seen above, if you want to pass multiple values you can send an array.
The DedicatedWorkerGlobalScope interface it belongs to.