doc: clarify process.argv[1] behavior for -e/--eval · nodejs/node@89a7f18
@@ -923,8 +923,8 @@ added: v0.1.27
923923The `process.argv` property returns an array containing the command-line
924924arguments passed when the Node.js process was launched. The first element will
925925be [`process.execPath`][]. See `process.argv0` if access to the original value
926-of `argv[0]` is needed. The second element will be the path to the JavaScript
927-file being executed. The remaining elements will be any additional command-line
926+of `argv[0]` is needed. If a [program entry point][] was provided, the second element
927+will be the absolute path to it. The remaining elements are additional command-line
928928arguments.
929929930930For example, assuming the following script for `process-args.js`:
@@ -4672,6 +4672,7 @@ cases:
46724672[process.cpuUsage]: #processcpuusagepreviousvalue
46734673[process_emit_warning]: #processemitwarningwarning-type-code-ctor
46744674[process_warning]: #event-warning
4675+[program entry point]: https://nodejs.org/api/cli.html#program-entry-point
46754676[report documentation]: report.md
46764677[terminal raw mode]: tty.md#readstreamsetrawmodemode
46774678[uv_get_available_memory]: https://docs.libuv.org/en/v1.x/misc.html#c.uv_get_available_memory