execFile for running executables in Node.js - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

Output of execFile with callback

What will be logged to the console when this Node.js code runs?

Node.js

import { execFile } from 'node:child_process';

execFile('node', ['-e', 'console.log("Hello from execFile")'], (error, stdout, stderr) => {
  if (error) {
    console.error('Error:', error.message);
    return;
  }
  if (stderr) {
    console.error('Stderr:', stderr);
    return;
  }
  console.log('Output:', stdout.trim());
});

A Output: Hello from execFile

B Error: spawn node ENOENT

C Stderr: Hello from execFile

D Output: undefined

💡 Hint

Look at how execFile runs the node executable with inline code and how stdout is handled.

The execFile runs the node executable with the inline script printing 'Hello from execFile'. The callback receives stdout with that output. No error or stderr occurs.

❓ component_behavior

intermediate

Behavior when executable path is incorrect

What happens when execFile is called with a non-existent executable path?

Node.js

import { execFile } from 'node:child_process';

execFile('/path/to/nonexistent', [], (error, stdout, stderr) => {
  if (error) {
    console.log(error.code);
  } else {
    console.log('No error');
  }
});

A ENOENT

B EACCES

C No error

D TypeError

💡 Hint

ENOENT means file or directory not found.

When the executable path does not exist, execFile returns an error with code 'ENOENT' indicating the file was not found.

🔧 Debug

advanced

Why does execFile callback never run?

Consider this code snippet. Why might the callback never be called?

Node.js

import { execFile } from 'node:child_process';

const child = execFile('node', ['-e', 'setTimeout(() => console.log("done"), 1000)']);

// No callback provided

console.log('Script finished');

A The child process never starts without a callback

B execFile requires a callback to run the child process

C The child process runs but output is not captured or logged

D Callback is missing, so no code runs after child process ends

💡 Hint

execFile can run without a callback but output won't be handled.

Without a callback, execFile runs the child process but does not capture or log its output. The callback is optional.

📝 Syntax

advanced

Correct usage of execFile with options

Which option correctly runs execFile with arguments and options to set working directory?

A execFile('ls', (err, stdout) => { console.log(stdout); }, ['-l'], { cwd: '/tmp' });

B execFile('ls', { cwd: '/tmp' }, ['-l'], (err, stdout) => { console.log(stdout); });

C execFile('ls', ['-l'], (err, stdout) => { console.log(stdout); }, { cwd: '/tmp' });

D execFile('ls', ['-l'], { cwd: '/tmp' }, (err, stdout) => { console.log(stdout); });

💡 Hint

Check the order of arguments: executable, args array, options object, callback.

execFile expects the arguments array as second, options object third, and callback last. Only option D follows this order.

🧠 Conceptual

expert

Why prefer execFile over exec for running executables?

Which reason best explains why execFile is preferred over exec when running executables directly?

A execFile supports streaming output, exec buffers all output in memory

B execFile does not spawn a shell, so it avoids shell injection risks and is more efficient

C execFile automatically retries on failure, exec does not

D execFile can run scripts without specifying the interpreter, exec cannot

💡 Hint

Think about security and performance differences between exec and execFile.

execFile runs the executable directly without a shell, reducing risk of shell injection and improving performance. exec runs commands inside a shell.

Practice

1. What is the main purpose of Node.js execFile function?

easy

A. To read files from the file system

B. To run JavaScript code inside a browser

C. To create a new Node.js server

D. To run an executable file directly without using a shell

Solution

1. Step 1: Understand execFile's role

   The execFile function is designed to run executable files directly, not scripts or servers.

2. Step 2: Compare with other Node.js functions

   Unlike exec, which runs commands in a shell, execFile runs the file directly, making it safer and faster.

3. Final Answer:

   To run an executable file directly without using a shell -> Option D

4. Quick Check:

   execFile runs executables directly = A [OK]

Hint: execFile runs programs directly, no shell involved [OK]

Common Mistakes:

• Confusing execFile with exec which uses a shell
• Thinking execFile runs JavaScript code in browser
• Assuming execFile reads or writes files

2. Which of the following is the correct syntax to import execFile from the child_process module in Node.js?

easy

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

B. import execFile from 'child_process';

C. const execFile = require('child_process').execFile();

D. const execFile = require('child_process').exec;

Solution

1. Step 1: Recall Node.js import syntax

   In Node.js CommonJS, destructuring import uses const { execFile } = require('child_process');.

2. Step 2: Check other options for errors

   import execFile from 'child_process'; uses ES module syntax incorrectly without braces. const execFile = require('child_process').execFile(); calls execFile immediately which is wrong. const execFile = require('child_process').execFile; misses destructuring braces.

3. Final Answer:

   const { execFile } = require('child_process'); -> Option A

4. Quick Check:

   Correct destructuring import = D [OK]

Hint: Use destructuring with require for execFile import [OK]

Common Mistakes:

• Using ES module import syntax without config
• Calling execFile as a function during import
• Not using destructuring braces

3. What will be the output of the following code snippet if ls is a valid executable on the system?

const { execFile } = require('child_process');
execFile('ls', ['-l'], (error, stdout, stderr) => {
  if (error) {
    console.error('Error:', error);
    return;
  }
  console.log('Output:', stdout);
});

medium

A. Error: ls is not recognized as a command

B. Output: (list of files and directories in long format)

C. Output: undefined

D. SyntaxError due to wrong callback

Solution

1. Step 1: Understand execFile usage

   The code runs the ls command with argument -l to list files in long format.

2. Step 2: Analyze callback behavior

   If ls exists, error is null and stdout contains the directory listing, printed as output.

3. Final Answer:

   Output: (list of files and directories in long format) -> Option B

4. Quick Check:

   execFile runs ls -l and outputs listing = B [OK]

Hint: execFile outputs stdout if no error occurs [OK]

Common Mistakes:

• Assuming execFile runs in a shell and fails
• Expecting error when executable exists
• Confusing stdout with undefined

4. Identify the error in this Node.js code using execFile:

const { execFile } = require('child_process');
execFile('node', ['-v'], (err, stdout) => {
  if (err) throw err;
  console.log(stdout);
  console.error(stderr);
});

medium

A. Callback function should not have parameters

B. Wrong executable name 'node'

C. Missing stderr parameter in callback

D. execFile cannot run 'node' command

Solution

1. Step 1: Check callback parameters

   The callback for execFile should have three parameters: error, stdout, and stderr.

2. Step 2: Identify missing parameter usage

   The code uses stderr but does not declare it in the callback parameters, causing a ReferenceError.

3. Final Answer:

   Missing stderr parameter in callback -> Option C

4. Quick Check:

   Callback must include stderr to use it = A [OK]

Hint: Callback needs error, stdout, stderr parameters [OK]

Common Mistakes:

• Forgetting stderr parameter in callback
• Assuming execFile can't run node
• Using wrong number of callback arguments

5. You want to run a custom executable ./script.sh with arguments arg1 and arg2 using execFile. Which code snippet correctly runs it and logs both output and errors safely?

hard

A. execFile('./script.sh', ['arg1', 'arg2'], (error, stdout, stderr) => {
if (error) {
console.error('Execution error:', error);
return;
}
if (stderr) {
console.error('Error output:', stderr);
}
console.log('Program output:', stdout);
});

B. execFile('./script.sh arg1 arg2', (error, stdout) => {
if (error) throw error;
console.log(stdout);
});

C. execFile('./script.sh', (error, stdout, stderr) => {
console.log(stdout);
console.log(stderr);
});

D. execFile(['./script.sh', 'arg1', 'arg2'], (error, stdout, stderr) => {
if (error) throw error;
console.log(stdout);
});

Solution

1. Step 1: Check argument passing

   Arguments must be passed as an array separate from the executable path, so ['arg1', 'arg2'] is correct.

2. Step 2: Verify error and output handling

   execFile('./script.sh', ['arg1', 'arg2'], (error, stdout, stderr) => { if (error) { console.error('Execution error:', error); return; } if (stderr) { console.error('Error output:', stderr); } console.log('Program output:', stdout); }); checks for execution errors, logs stderr if present, and prints stdout, which is safe and complete.

3. Final Answer:

   execFile('./script.sh', ['arg1', 'arg2'], (error, stdout, stderr) => { ... }) -> Option A

4. Quick Check:

   Pass args array and handle error, stderr, stdout = C [OK]

Hint: Pass args as array, handle error and stderr separately [OK]

Common Mistakes:

• Passing all args in one string instead of array
• Ignoring stderr output
• Passing args as first parameter array