GeezerVison is showing github.com — doc: clarify process.argv[1] behavior for -e/--eval · nodejs/node@3331bdc
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/api/process.md +3-2Lines changed: 3 additions & 2 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -834,8 +834,8 @@ added: v0.1.27 |
834 | 834 | The `process.argv` property returns an array containing the command-line |
835 | 835 | arguments passed when the Node.js process was launched. The first element will |
836 | 836 | be [`process.execPath`][]. See `process.argv0` if access to the original value |
837 | | -of `argv[0]` is needed. The second element will be the path to the JavaScript |
838 | | -file being executed. The remaining elements will be any additional command-line |
| 837 | +of `argv[0]` is needed. If a [program entry point][] was provided, the second element |
| 838 | +will be the absolute path to it. The remaining elements are additional command-line |
839 | 839 | arguments. |
840 | 840 |
|
841 | 841 | For example, assuming the following script for `process-args.js`: |
@@ -4590,6 +4590,7 @@ cases: |
4590 | 4590 | [process.cpuUsage]: #processcpuusagepreviousvalue |
4591 | 4591 | [process_emit_warning]: #processemitwarningwarning-type-code-ctor |
4592 | 4592 | [process_warning]: #event-warning |
| 4593 | +[program entry point]: https://nodejs.org/api/cli.html#program-entry-point |
4593 | 4594 | [report documentation]: report.md |
4594 | 4595 | [terminal raw mode]: tty.md#readstreamsetrawmodemode |
4595 | 4596 | [uv_get_available_memory]: https://docs.libuv.org/en/v1.x/misc.html#c.uv_get_available_memory |
|