process.argv for command line arguments in Node.js - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ Predict Output

intermediate

What is the output of this Node.js script?

Consider this Node.js script run with the command: node script.js hello world. What will it print?

Node.js

console.log(process.argv.slice(2));

A ["hello world"]

B ["node", "script.js", "hello", "world"]

C ["script.js", "hello", "world"]

D ["hello", "world"]

💡 Hint

Remember that process.argv includes the node executable and script path as the first two items.

The process.argv array contains the node executable path at index 0 and the script path at index 1. Using slice(2) returns only the arguments passed after the script name, which are "hello" and "world".

❓ state_output

intermediate

What is the value of args after running this code?

If the script is run as node app.js --name=John --age=30, what is the value of args?

Node.js

const args = process.argv.slice(2);
console.log(args);

A ["--name=John", "--age=30"]

B ["name", "John", "age", "30"]

C ["--name", "John", "--age", "30"]

D ["app.js", "--name=John", "--age=30"]

💡 Hint

Arguments are passed as strings exactly as typed after the script name.

The process.argv array includes the arguments as strings exactly as typed. Since the arguments are passed as --name=John and --age=30, slicing from index 2 returns those exact strings.

📝 Syntax

advanced

Which option correctly extracts the third command line argument?

Given the command node index.js a b c d, which code correctly assigns the third argument to variable thirdArg?

A const thirdArg = process.argv[2];

B const thirdArg = process.argv[4];

C const thirdArg = process.argv.slice(2)[3];

D const thirdArg = process.argv.slice(3);

💡 Hint

Remember that process.argv[0] is node path, [1] is script path, so arguments start at index 2.

The process.argv array contains the node executable path at index 0 and the script path at index 1. Arguments start at index 2: 'a' (2), 'b' (3), 'c' (4), 'd' (5). The third argument is 'c' at index 4.

Option B gets the first argument ('a' at index 2).

Option B returns an array from index 3 onward (['b', 'c', 'd']).

Option B: process.argv[4] gets the third argument ('c').

Option B gets the fourth element of the sliced array starting at 2, which is 'd' (index 5 overall).

🔧 Debug

advanced

Why does this code print an empty array when run with arguments?

Given this code and running node app.js test, why does it print []?

Node.js

const args = process.argv.slice(3);
console.log(args);

A Because slice(3) returns the first three elements, which are empty.

B Because process.argv is empty when arguments are passed.

C Because slice(3) skips the first three elements, but only two exist after index 2.

D Because console.log cannot print arrays from process.argv.

💡 Hint

Check how many elements process.argv has when running with one argument.

process.argv has at least two elements: node path and script path. Arguments start at index 2. With one argument 'test', process.argv has length 3. Using slice(3) returns elements starting at index 3, which is beyond the last element, so it returns an empty array.

🧠 Conceptual

expert

What is the length of process.argv when running node without a script?

If you run node alone (no script, no arguments), what is the length of process.argv inside the Node.js REPL?

A 2

B 0

C 3

D 1

💡 Hint

Think about what process.argv contains by default: node path and script path.

Even when no script is provided, process.argv contains the path to the node executable at index 0 and the path to the REPL script at index 1, so its length is 2.

Practice

1. What does process.argv contain in a Node.js program?

easy

A. An array of command line arguments including Node.js path and script path

B. Only the user input arguments passed to the script

C. The environment variables of the system

D. The output of the last executed command

Solution

1. Step 1: Understand what process.argv holds

   process.argv is an array that contains the full command line arguments used to start the Node.js process.

2. Step 2: Identify the contents of the array

   The first element is the path to the Node.js executable, the second is the path to the script file, and the rest are user inputs.

3. Final Answer:

   An array of command line arguments including Node.js path and script path -> Option A

4. Quick Check:

   process.argv includes Node and script paths [OK]

Hint: Remember first two items are paths, user args start at index 2 [OK]

Common Mistakes:

• Thinking process.argv only has user inputs
• Confusing process.argv with environment variables
• Assuming process.argv is a string, not an array

2. Which of the following is the correct way to get only the user input arguments from process.argv?

easy

A. process.argv.slice(0)

B. process.argv.slice(1)

C. process.argv.slice(2)

D. process.argv.slice(3)

Solution

1. Step 1: Recall the structure of process.argv

   The first two elements are fixed paths: Node.js executable and script file.

2. Step 2: Use slice(2) to skip these and get user inputs

   Using process.argv.slice(2) returns an array starting from the third element, which are the user arguments.

3. Final Answer:

   process.argv.slice(2) -> Option C

4. Quick Check:

   Slice from index 2 to get user args [OK]

Hint: Slice from 2 to skip Node and script paths [OK]

Common Mistakes:

• Using slice(0) returns all including paths
• Using slice(1) includes script path as argument
• Using slice(3) skips first user argument

3. What will be the output of this Node.js script if run as node script.js hello world?

console.log(process.argv.slice(2));

medium

A. ["node", "script.js", "hello", "world"]

B. ["hello", "world"]

C. ["script.js", "hello", "world"]

D. SyntaxError

Solution

1. Step 1: Understand the command line input

   The command node script.js hello world passes "hello" and "world" as user arguments.

2. Step 2: Analyze process.argv.slice(2)

   This slices the array to exclude the first two elements (node path and script path), leaving only user inputs.

3. Final Answer:

   ["hello", "world"] -> Option B

4. Quick Check:

   Slice(2) returns only user args [OK]

Hint: Slice(2) returns only user inputs, not paths [OK]

Common Mistakes:

• Including node and script paths in output
• Confusing array contents with strings
• Expecting syntax error for valid code

4. Identify the error in this code snippet that tries to print user arguments:

console.log(process.argv[0]);

medium

A. It prints the script file path

B. It causes a runtime error because index 0 is undefined

C. It prints the first user argument correctly

D. It prints the Node.js executable path, not user arguments

Solution

1. Step 1: Check what process.argv[0] holds

   The first element is the path to the Node.js executable, not user input.

2. Step 2: Understand why this is a mistake

   To get user arguments, you must start from index 2, so using index 0 prints the wrong value.

3. Final Answer:

   It prints the Node.js executable path, not user arguments -> Option D

4. Quick Check:

   Index 0 is Node path, not user args [OK]

Hint: User args start at index 2, not 0 [OK]

Common Mistakes:

• Assuming index 0 is first user argument
• Expecting runtime error for valid index
• Confusing script path with user input

5. You want to write a Node.js script that sums two numbers passed as command line arguments. Which code correctly extracts and sums the inputs?

const args = process.argv.slice(2);
const sum = Number(args[0]) + Number(args[1]);
console.log(sum);

hard

A. Correctly sums two user inputs as numbers

B. Fails because process.argv does not contain user inputs

C. Fails because slice(2) removes user inputs

D. Fails because Number() cannot convert strings

Solution

1. Step 1: Extract user inputs correctly

   Using process.argv.slice(2) gets only user arguments, which are strings representing numbers.

2. Step 2: Convert strings to numbers and sum

   Using Number() converts string inputs to numbers, allowing correct addition.

3. Final Answer:

   Correctly sums two user inputs as numbers -> Option A

4. Quick Check:

   Slice(2) + Number() converts and sums inputs [OK]

Hint: Slice(2) then Number() to convert strings to numbers [OK]

Common Mistakes:

• Not slicing to get user inputs
• Adding strings without conversion causing concatenation
• Assuming Number() cannot convert numeric strings