Hey there! Let's break down how to handle CMD commands in Node.js and package your script into a standalone executable—super useful for distributing your tools without requiring Node.js to be installed.

Node.js内置的child_process模块 is your go-to tool for running external commands. It offers a few different methods, each suited to different scenarios:

1. 使用exec方法（适合获取完整输出） #

exec runs commands in a shell and buffers the entire output, making it perfect for simple commands with small output (like dir or echo):

const { exec } = require('child_process');

// Run a CMD command to list directory contents
exec('dir', (error, stdout, stderr) => {
  if (error) {
    console.error(`Command failed: ${error.message}`);
    return;
  }
  if (stderr) {
    console.error(`Error output: ${stderr}`);
    return;
  }
  console.log(`Command output:\n${stdout}`);
});

For commands with arguments, just append them to the string—like exec('echo Hello, Node.js!').

2. 使用spawn方法（适合流式处理大输出） #

spawn is a lower-level method that streams output instead of buffering it. Use this for commands that produce large amounts of data (like log parsing) or when you need real-time output:

const { spawn } = require('child_process');

// Call CMD's dir command—note the structure here
const dirProcess = spawn('cmd.exe', ['/c', 'dir']);

// Listen to standard output stream
dirProcess.stdout.on('data', (data) => {
  console.log(`Output: ${data}`);
});

// Listen to error output stream
dirProcess.stderr.on('data', (data) => {
  console.error(`Error: ${data}`);
});

// Listen for process exit
dirProcess.on('close', (code) => {
  console.log(`Process exited with code: ${code}`);
});

When calling CMD-specific commands, use cmd.exe as the command, with /c to tell CMD to close after executing the command, followed by your actual command.

3. 使用execFile方法（更安全，避免 shell 注入） #

execFile runs executable files directly without a shell by default, which is more secure (prevents shell injection risks). Great for running trusted executables:

const { execFile } = require('child_process');

// Run cmd.exe with a command passed as arguments
execFile('cmd.exe', ['/c', 'echo Hello from CMD!'], (error, stdout, stderr) => {
  if (error) {
    console.error(`Command failed: ${error}`);
    return;
  }
  console.log(stdout.trim());
});

If you need shell features (like pipes or redirects), add the { shell: true } option to enable it.

If you want your Node.js script to run like a native CMD program (no Node.js installation required for end users), use a packaging tool to turn it into a Windows .exe file. pkg is one of the most popular options:

Step 1: Install the pkg tool #

First, install pkg globally:

npm install -g pkg

Step 2: Configure your script #

Make sure your script has a clear entry point (like index.js) and update your package.json to specify it:

{
  "name": "my-cmd-tool",
  "version": "1.0.0",
  "main": "index.js",
  "bin": "index.js"
}

If your script needs command-line arguments, use process.argv to grab them:

// index.js
const args = process.argv.slice(2);
console.log(`Your input arguments: ${args.join(' ')}`);

Step 3: Package into an executable #

Run this command in your project root to build a Windows 64-bit executable:

pkg . --targets win32-x64

Once done, you'll get an .exe file (e.g., my-cmd-tool.exe) that can be double-clicked to run in CMD, or executed directly from the command line.

Quick Notes #

• If your script uses static files (like configs or templates), include them in the build with the --assets flag: pkg . --targets win32-x64 --assets "config/**/*"
• The resulting .exe will be larger than your script because it includes the Node.js runtime—this is normal.

内容的提问来源于stack exchange，提问作者Digital Nomad