René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"child_process.spawn fails on Windows given a space in both the command and an argument","articleBody":"\u003c!--\nThank you for reporting an issue. Please fill in the template below. If unsure\nabout something, just do as best as you're able.\n\nVersion: usually output of `node -v`\nPlatform: either `uname -a` output, or if Windows, version and 32 or 64-bit\nSubsystem: if known, please specify affected core module name\n\nIf possible, please provide code that demonstrates the problem, keeping it as\nsimple and free of external dependencies as you are able.\n--\u003e\n- **Version**: 4.4.4, 4.4.7, 5.10.1, 6.2.2\n- **Platform**: Windows 7, 64-bit\n- **Subsystem**: `child_process`\n\n\u003c!-- Enter your issue details below this comment. --\u003e\n\nReproduction of the error: https://gist.github.com/smrq/f028b22bc748af9e68a7\n\nOn Windows, `child_process.spawn` handles the command incorrectly when both it and one of its arguments contains a space. So, this works fine:\n\n```\nvar spawn = require('child_process').spawn;\n\nspawn('nospaces.cmd', ['arg with spaces']);\nspawn('command with spaces.cmd', ['nospaces']);\n```\n\nBut this yields `'command' is not recognized as an internal or external command, operable program or batch file.`:\n\n```\nspawn('command with spaces.cmd', ['arg with spaces']);\n```\n\n(This is [node-v0.x-archive #25895](https://github.com/nodejs/node-v0.x-archive/issues/25895), still extant in higher Node.js versions.)\n","author":{"url":"https://github.com/s100","@type":"Person","name":"s100"},"datePublished":"2016-06-22T14:17:16.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":20},"url":"https://github.com/7367/node/issues/7367"}