Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
doc: clarify process.argv[1] behavior for -e/--eval
Signed-off-by: Jeevankumar-S <jeevenkumar2003@email.com>
  • Loading branch information
Jeevankumar-S
Jeevankumar-S committed Jan 13, 2026
commit 0c72802757e6ba4e93bd9917bf9e3ebfc4cbcf06
6 changes: 1 addition & 5 deletions doc/api/process.md
Original file line number Diff line number Diff line change
Expand Up @@ -832,11 +832,7 @@ added: v0.1.27
* Type: {string\[]}

The `process.argv` property returns an array containing the command-line
arguments passed when the Node.js process was launched. The first element will
be [`process.execPath`][]. See `process.argv0` if access to the original value
of `argv[0]` is needed. The second element will be the path to the JavaScript
file being executed. The remaining elements will be any additional command-line
arguments.
arguments passed when the Node.js process was launched. The first element will be [process.execPath][]. See process.argv0 if access to the original value of argv[0] is needed. The second element will be the path to the JavaScript file being executed (if a script file is provided). For no-script execution modes (e.g., -e/--eval), the second element is the first unconsumed command-line argument. The remaining elements are additional command-line arguments.

For example, assuming the following script for `process-args.js`:

Expand Down