René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"[v22.2.0 regression] Some `Worker` use cases are broken","articleBody":"### Version\r\n\r\nv22.2.0\r\n\r\n### Platform\r\n\r\nall\r\n\r\n### Subsystem\r\n\r\nworker_threads\r\n\r\n### What steps will reproduce the bug?\r\n\r\n```js\r\nimport { Worker, isMainThread } from \"worker_threads\";\r\n\r\nif (isMainThread) {\r\n  new Worker(import.meta.filename, { env: process.env });\r\n} else {\r\n  console.log(\"Hello, world!\");\r\n}\r\n\r\n```\r\n`node --expose_gc .\\test.mjs`\r\n\r\n### How often does it reproduce? Is there a required condition?\r\n\r\nalways\r\n\r\n### What is the expected behavior? Why is that the expected behavior?\r\n\r\nHello, world!\r\n\r\n### What do you see instead?\r\n\r\n```\r\nnode:internal/worker:221\r\n      throw new ERR_WORKER_INVALID_EXEC_ARGV(this[kHandle].invalidExecArgv);\r\n            ^\r\n\r\nError [ERR_WORKER_INVALID_EXEC_ARGV]: Initiated Worker with invalid execArgv flags: --expose_gc\r\n    at new Worker (node:internal/worker:221:13)\r\n    at file:///F:/babel/test.mjs:4:3\r\n    at ModuleJob.run (node:internal/modules/esm/module_job:262:25)\r\n    at async ModuleLoader.import (node:internal/modules/esm/loader:475:24)\r\n    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:109:5) {\r\n  code: 'ERR_WORKER_INVALID_EXEC_ARGV'\r\n}\r\n```\r\n\r\n### Additional information\r\n\r\nRef: https://github.com/nodejs/node/pull/52827\r\nIt seems that passing execArgv will cause some problems until https://github.com/nodejs/node/issues/41103 is resolved.\r\n\r\nI'm not sure this is a regression, but it could be an unintentional breakage and would be a bit difficult to resolve on the user side since there are no known exec argvs supported by `Worker`.\r\n\r\ncc @theanarkh You may be interested!","author":{"url":"https://github.com/liuxingbaoyu","@type":"Person","name":"liuxingbaoyu"},"datePublished":"2024-05-15T21:26:51Z","url":"https://github.com/nodejs/node/issues/53011"}