The worker_threads module enables the use of threads that execute JavaScript\nin parallel. To access it:
const worker = require('worker_threads');\nWorkers (threads) are useful for performing CPU-intensive JavaScript operations.\nThey will not help much with I/O-intensive work. Node.js’s built-in asynchronous\nI/O operations are more efficient than Workers can be.
\nUnlike child_process or cluster, worker_threads can share memory. They do\nso by transferring ArrayBuffer instances or sharing SharedArrayBuffer\ninstances.
const {\n Worker, isMainThread, parentPort, workerData\n} = require('worker_threads');\n\nif (isMainThread) {\n module.exports = function parseJSAsync(script) {\n return new Promise((resolve, reject) => {\n const worker = new Worker(__filename, {\n workerData: script\n });\n worker.on('message', resolve);\n worker.on('error', reject);\n worker.on('exit', (code) => {\n if (code !== 0)\n reject(new Error(`Worker stopped with exit code ${code}`));\n });\n });\n };\n} else {\n const { parse } = require('some-js-parsing-library');\n const script = workerData;\n parentPort.postMessage(parse(script));\n}\nThe above example spawns a Worker thread for each parse() call. In actual\npractice, use a pool of Workers instead for these kinds of tasks. Otherwise, the\noverhead of creating Workers would likely exceed their benefit.
Is true if this code is not running inside of a Worker thread.
const { Worker, isMainThread } = require('worker_threads');\n\nif (isMainThread) {\n // This re-loads the current file inside a Worker instance.\n new Worker(__filename);\n} else {\n console.log('Inside Worker!');\n console.log(isMainThread); // Prints 'false'.\n}\nIf this thread was spawned as a Worker, this will be a MessagePort\nallowing communication with the parent thread. Messages sent using\nparentPort.postMessage() will be available in the parent thread\nusing worker.on('message'), and messages sent from the parent thread\nusing worker.postMessage() will be available in this thread using\nparentPort.on('message').
const { Worker, isMainThread, parentPort } = require('worker_threads');\n\nif (isMainThread) {\n const worker = new Worker(__filename);\n worker.once('message', (message) => {\n console.log(message); // Prints 'Hello, world!'.\n });\n worker.postMessage('Hello, world!');\n} else {\n // When a message from the parent thread is received, send it back:\n parentPort.once('message', (message) => {\n parentPort.postMessage(message);\n });\n}\nA special value that can be passed as the env option of the Worker\nconstructor, to indicate that the current thread and the Worker thread should\nshare read and write access to the same set of environment variables.
const { Worker, SHARE_ENV } = require('worker_threads');\nnew Worker('process.env.SET_IN_WORKER = \"foo\"', { eval: true, env: SHARE_ENV })\n .on('exit', () => {\n console.log(process.env.SET_IN_WORKER); // Prints 'foo'.\n });\nAn integer identifier for the current thread. On the corresponding worker object\n(if there is any), it is available as worker.threadId.\nThis value is unique for each Worker instance inside a single process.
An arbitrary JavaScript value that contains a clone of the data passed\nto this thread’s Worker constructor.
The data is cloned as if using postMessage(),\naccording to the HTML structured clone algorithm.
const { Worker, isMainThread, workerData } = require('worker_threads');\n\nif (isMainThread) {\n const worker = new Worker(__filename, { workerData: 'Hello, world!' });\n} else {\n console.log(workerData); // Prints 'Hello, world!'.\n}\nTransfer a MessagePort to a different vm Context. The original port\nobject will be rendered unusable, and the returned MessagePort instance will\ntake its place.
The returned MessagePort will be an object in the target context, and will\ninherit from its global Object class. Objects passed to the\nport.onmessage() listener will also be created in the target context\nand inherit from its global Object class.
However, the created MessagePort will no longer inherit from\nEventEmitter, and only port.onmessage() can be used to receive\nevents using it.
Receive a single message from a given MessagePort. If no message is available,\nundefined is returned, otherwise an object with a single message property\nthat contains the message payload, corresponding to the oldest message in the\nMessagePort’s queue.
const { MessageChannel, receiveMessageOnPort } = require('worker_threads');\nconst { port1, port2 } = new MessageChannel();\nport1.postMessage({ hello: 'world' });\n\nconsole.log(receiveMessageOnPort(port2));\n// Prints: { message: { hello: 'world' } }\nconsole.log(receiveMessageOnPort(port2));\n// Prints: undefined\nWhen this function is used, no 'message' event will be emitted and the\nonmessage listener will not be invoked.
Instances of the worker.MessageChannel class represent an asynchronous,\ntwo-way communications channel.\nThe MessageChannel has no methods of its own. new MessageChannel()\nyields an object with port1 and port2 properties, which refer to linked\nMessagePort instances.
const { MessageChannel } = require('worker_threads');\n\nconst { port1, port2 } = new MessageChannel();\nport1.on('message', (message) => console.log('received', message));\nport2.postMessage({ foo: 'bar' });\n// Prints: received { foo: 'bar' } from the `port1.on('message')` listener\nInstances of the worker.MessagePort class represent one end of an\nasynchronous, two-way communications channel. It can be used to transfer\nstructured data, memory regions and other MessagePorts between different\nWorkers.
With the exception of MessagePorts being EventEmitters rather\nthan EventTargets, this implementation matches browser MessagePorts.
The 'close' event is emitted once either side of the channel has been\ndisconnected.
const { MessageChannel } = require('worker_threads');\nconst { port1, port2 } = new MessageChannel();\n\n// Prints:\n// foobar\n// closed!\nport2.on('message', (message) => console.log(message));\nport2.on('close', () => console.log('closed!'));\n\nport1.postMessage('foobar');\nport1.close();\nThe 'message' event is emitted for any incoming message, containing the cloned\ninput of port.postMessage().
Listeners on this event will receive a clone of the value parameter as passed\nto postMessage() and no further arguments.
Disables further sending of messages on either side of the connection.\nThis method can be called when no further communication will happen over this\nMessagePort.
The 'close' event will be emitted on both MessagePort instances that\nare part of the channel.
Sends a JavaScript value to the receiving side of this channel.\nvalue will be transferred in a way which is compatible with\nthe HTML structured clone algorithm.
In particular, the significant differences to JSON are:
value may contain circular references.value may contain instances of builtin JS types such as RegExps,\nBigInts, Maps, Sets, etc.value may contained typed arrays, both using ArrayBuffers\nand SharedArrayBuffers.value may contain WebAssembly.Module instances.value may not contain native (C++-backed) objects other than MessagePorts.const { MessageChannel } = require('worker_threads');\nconst { port1, port2 } = new MessageChannel();\n\nport1.on('message', (message) => console.log(message));\n\nconst circularData = {};\ncircularData.foo = circularData;\n// Prints: { foo: [Circular] }\nport2.postMessage(circularData);\ntransferList may be a list of ArrayBuffer and MessagePort objects.\nAfter transferring, they will not be usable on the sending side of the channel\nanymore (even if they are not contained in value). Unlike with\nchild processes, transferring handles such as network sockets is currently\nnot supported.
If value contains SharedArrayBuffer instances, those will be accessible\nfrom either thread. They cannot be listed in transferList.
value may still contain ArrayBuffer instances that are not in\ntransferList; in that case, the underlying memory is copied rather than moved.
const { MessageChannel } = require('worker_threads');\nconst { port1, port2 } = new MessageChannel();\n\nport1.on('message', (message) => console.log(message));\n\nconst uint8Array = new Uint8Array([ 1, 2, 3, 4 ]);\n// This posts a copy of `uint8Array`:\nport2.postMessage(uint8Array);\n// This does not copy data, but renders `uint8Array` unusable:\nport2.postMessage(uint8Array, [ uint8Array.buffer ]);\n\n// The memory for the `sharedUint8Array` will be accessible from both the\n// original and the copy received by `.on('message')`:\nconst sharedUint8Array = new Uint8Array(new SharedArrayBuffer(4));\nport2.postMessage(sharedUint8Array);\n\n// This transfers a freshly created message port to the receiver.\n// This can be used, for example, to create communication channels between\n// multiple `Worker` threads that are children of the same parent thread.\nconst otherChannel = new MessageChannel();\nport2.postMessage({ port: otherChannel.port1 }, [ otherChannel.port1 ]);\nBecause the object cloning uses the structured clone algorithm,\nnon-enumerable properties, property accessors, and object prototypes are\nnot preserved. In particular, Buffer objects will be read as\nplain Uint8Arrays on the receiving side.
The message object will be cloned immediately, and can be modified after\nposting without having side effects.
\nFor more information on the serialization and deserialization mechanisms\nbehind this API, see the serialization API of the v8 module.
Opposite of unref(). Calling ref() on a previously unref()ed port will\nnot let the program exit if it's the only active handle left (the default\nbehavior). If the port is ref()ed, calling ref() again will have no effect.
If listeners are attached or removed using .on('message'), the port will\nbe ref()ed and unref()ed automatically depending on whether\nlisteners for the event exist.
Starts receiving messages on this MessagePort. When using this port\nas an event emitter, this will be called automatically once 'message'\nlisteners are attached.
This method exists for parity with the Web MessagePort API. In Node.js,\nit is only useful for ignoring messages when no event listener is present.\nNode.js also diverges in its handling of .onmessage. Setting it will\nautomatically call .start(), but unsetting it will let messages queue up\nuntil a new handler is set or the port is discarded.
Calling unref() on a port will allow the thread to exit if this is the only\nactive handle in the event system. If the port is already unref()ed calling\nunref() again will have no effect.
If listeners are attached or removed using .on('message'), the port will\nbe ref()ed and unref()ed automatically depending on whether\nlisteners for the event exist.
The Worker class represents an independent JavaScript execution thread.\nMost Node.js APIs are available inside of it.
Notable differences inside a Worker environment are:
\nprocess.stdin, process.stdout and process.stderr\nmay be redirected by the parent thread.require('worker_threads').isMainThread property is set to false.require('worker_threads').parentPort message port is available.process.exit() does not stop the whole program, just the single thread,\nand process.abort() is not available.process.chdir() and process methods that set group or user ids\nare not available.process.env is a copy of the parent thread's environment variables,\nunless otherwise specified. Changes to one copy will not be visible in other\nthreads, and will not be visible to native add-ons (unless\nworker.SHARE_ENV has been passed as the env option to the\nWorker constructor).process.title cannot be modified.process.on('...').worker.terminate()\nbeing invoked.trace_events module is not supported.Creating Worker instances inside of other Workers is possible.
Like Web Workers and the cluster module, two-way communication can be\nachieved through inter-thread message passing. Internally, a Worker has a\nbuilt-in pair of MessagePorts that are already associated with each other\nwhen the Worker is created. While the MessagePort object on the parent side\nis not directly exposed, its functionalities are exposed through\nworker.postMessage() and the worker.on('message') event\non the Worker object for the parent thread.
To create custom messaging channels (which is encouraged over using the default\nglobal channel because it facilitates separation of concerns), users can create\na MessageChannel object on either thread and pass one of the\nMessagePorts on that MessageChannel to the other thread through a\npre-existing channel, such as the global one.
See port.postMessage() for more information on how messages are passed,\nand what kind of JavaScript values can be successfully transported through\nthe thread barrier.
const assert = require('assert');\nconst {\n Worker, MessageChannel, MessagePort, isMainThread, parentPort\n} = require('worker_threads');\nif (isMainThread) {\n const worker = new Worker(__filename);\n const subChannel = new MessageChannel();\n worker.postMessage({ hereIsYourPort: subChannel.port1 }, [subChannel.port1]);\n subChannel.port2.on('message', (value) => {\n console.log('received:', value);\n });\n} else {\n parentPort.once('message', (value) => {\n assert(value.hereIsYourPort instanceof MessagePort);\n value.hereIsYourPort.postMessage('the worker is sending this');\n value.hereIsYourPort.close();\n });\n}\nThe 'error' event is emitted if the worker thread throws an uncaught\nexception. In that case, the worker will be terminated.
The 'exit' event is emitted once the worker has stopped. If the worker\nexited by calling process.exit(), the exitCode parameter will be the\npassed exit code. If the worker was terminated, the exitCode parameter will\nbe 1.
The 'message' event is emitted when the worker thread has invoked\nrequire('worker_threads').parentPort.postMessage().\nSee the port.on('message') event for more details.
The 'online' event is emitted when the worker thread has started executing\nJavaScript code.
Send a message to the worker that will be received via\nrequire('worker_threads').parentPort.on('message').\nSee port.postMessage() for more details.
Opposite of unref(), calling ref() on a previously unref()ed worker will\nnot let the program exit if it's the only active handle left (the default\nbehavior). If the worker is ref()ed, calling ref() again will have\nno effect.
Stop all JavaScript execution in the worker thread as soon as possible.\ncallback is an optional function that is invoked once this operation is known\nto have completed.
Warning: Currently, not all code in the internals of Node.js is prepared to\nexpect termination at arbitrary points in time and may crash if it encounters\nthat condition. Consequently, only call .terminate() if it is known that the\nWorker thread is not accessing Node.js core modules other than what is exposed\nin the worker module.
Calling unref() on a worker will allow the thread to exit if this is the only\nactive handle in the event system. If the worker is already unref()ed calling\nunref() again will have no effect.
This is a readable stream which contains data written to process.stderr\ninside the worker thread. If stderr: true was not passed to the\nWorker constructor, then data will be piped to the parent thread's\nprocess.stderr stream.
If stdin: true was passed to the Worker constructor, this is a\nwritable stream. The data written to this stream will be made available in\nthe worker thread as process.stdin.
This is a readable stream which contains data written to process.stdout\ninside the worker thread. If stdout: true was not passed to the\nWorker constructor, then data will be piped to the parent thread's\nprocess.stdout stream.
An integer identifier for the referenced thread. Inside the worker thread,\nit is available as require('worker_threads').threadId.\nThis value is unique for each Worker instance inside a single process.