René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Worker Threads: Add transferList to Worker constructor options","articleBody":"**Is your feature request related to a problem? Please describe.**\r\n\r\nBased on the current documentation listed [here](https://nodejs.org/api/worker_threads.html#worker_threads_new_worker_filename_options), it doesn't seem possible to specify a `transferList` on the Worker constructor. This prohibits passing `transferList` items such as `MessagePort`. Attempts to pass a `MessagePort` within the Workers `workerData` currently results in the following error.\r\n```\r\nTypeError: MessagePort was found in message but not listed in transferList\r\n```\r\n**Describe the solution you'd like**\r\n\r\nGiven the current error, and if its technically feasible to do so...being able to supply a `transferList` on the `Worker` constructor would be helpful in initializing the Worker immediately with a `MessagePort` rather than sending the `MessagePort` on a subsequent `postMessage(...)`. Perhaps something like the following could be allowed.\r\n\r\n```javascript\r\nconst channel = new MessageChannel()\r\nconst workerData = { port: channel.port1 }\r\nconst transferList = [channel.port1]\r\nconst worker = new Worker('./worker.js', { workerData, transferList  })\r\n```\r\n\r\n\r\n**Describe alternatives you've considered**\r\n\r\nIt is entirely possible to work around this by sending a `MessagePort` in a subsequent `postMessage(..., transferList)`. However it doing so involves async initialization of the `Worker` which is less desirable than initializing immediately on the `Worker` constructor.\r\n","author":{"url":"https://github.com/sinclairzx81","@type":"Person","name":"sinclairzx81"},"datePublished":"2020-03-13T15:34:53.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/32250/node/issues/32250"}