`util.parseArgs()` omits the first positional argument when used with the `--eval=` option

[kit494way]

Version

v25.2.1

Platform

Linux DESKTOP-O26JEMV 6.6.87.2-microsoft-standard-WSL2 #1 SMP PREEMPT_DYNAMIC Thu Jun  5 18:30:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

Subsystem

No response

What steps will reproduce the bug?

node --eval="import {parseArgs} from 'node:util';console.log(parseArgs({allowPositionals: true}))" -- arg1 arg2

How often does it reproduce? Is there a required condition?

Always

What is the expected behavior? Why is that the expected behavior?

{
  values: [Object: null prototype] {},
  positionals: [ 'arg1', 'arg2' ]
}

What do you see instead?

{ values: [Object: null prototype] {}, positionals: [ 'arg2' ] }

Additional information

No response

[ljharb]

hmm, this is specifically accounted for in the code.

[Renegade334]

hmm, this is specifically accounted for in the code.

Looks like --eval ... is covered, but --eval=... isn't.

[azadgupta1]

I would like to work on this issue.
I’ll start investigating the --eval= case where the first positional arg is skipped
and will share findings or a draft fix soon.

[IlyasShabi]

I think that the issue is:

• When we use --eval "code" we store it in process.execArgv as TWO separate items ['--eval', 'code']
• When we use --eval="code" we store it as ONE item ['--eval=code']

We should check if any item execArgv starts with --eval not just exact match as we do today.

@azadgupta1 If you're willing to fix this the function you need to modify is getMainArgs()

Nb: This bug affects both --eval= and --print

Let me know if you need any help