René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Node CLI eval option can't take unary negation operator","articleBody":"### Version\n\nv17.9.0\n\n### Platform\n\nDarwin [redacted] 19.6.0 Darwin Kernel Version 19.6.0: Tue Feb 15 21:39:11 PST 2022; root:xnu-6153.141.59~1/RELEASE_X86_64 x86_64\n\n### Subsystem\n\n_No response_\n\n### What steps will reproduce the bug?\n\nExecute the following:\r\n\r\n```bash\r\n$ node -pe \"-0\"\r\n```\r\n\r\nAnd you will get back:\r\n\r\n```\r\nnode: --eval requires an argument\r\n```\r\n\r\nIn fact, anything where the `-` comes first, you get this message.\r\n\r\nFor example, all of the following also result in the above message:\r\n\r\n```bash\r\n$ node -pe \"-42\"\r\n$ node -pe \"-\"\r\n$ node -pe \"-NaN\"\r\n```\r\n\n\n### How often does it reproduce? Is there a required condition?\n\nIt's always reproducable (at least on this version and machine).\n\n### What is the expected behavior?\n\nI'd like it to *not* spit back an error message and give me the evaluated value, please.\n\n### What do you see instead?\n\nAn error message detailing that the \"eval\" option was not given a value.\n\n### Additional information\n\n\r\nIt seems that the CLI is not properly parsing its arguments?\r\n\r\nPrefixing the expression with `0` seems to work:\r\n\r\n```bash\r\n$ node -pe \"0-42\"\r\n42\r\n```\r\n\r\nAs well as using a comma operator:\r\n\r\n```bash\r\n$ node -pe \"(0, -42)\"\r\n-42\r\n```\r\n","author":{"url":"https://github.com/k-tten","@type":"Person","name":"k-tten"},"datePublished":"2022-06-13T00:45:14.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/43397/node/issues/43397"}