util: fix parseArgs skipping first positional arg with --eval= and --print=

Author: azadgupta1

lib/internal/util/parse_args/parse_args.js

@@ -56,21 +56,22 @@ const {
 
 
 function getMainArgs() {
-  // Work out where to slice process.argv for user supplied arguments.
-
-  // Check node options for scenarios where user CLI args follow executable.
   const execArgv = process.execArgv;
-  if (ArrayPrototypeIncludes(execArgv, '-e') ||
-      ArrayPrototypeIncludes(execArgv, '--eval') ||
-      ArrayPrototypeIncludes(execArgv, '-p') ||
-      ArrayPrototypeIncludes(execArgv, '--print')) {
+
+  const hasEvalOrPrint = execArgv.some(arg =>
+    arg === '-e' || arg === '--eval' ||
+    arg === '-p' || arg === '--print' ||
+    arg.startsWith('--eval=') || arg.startsWith('--print=')
+  );
+
+  if (hasEvalOrPrint) {
     return ArrayPrototypeSlice(process.argv, 1);
   }
 
-  // Normally first two arguments are executable and script, then CLI arguments
   return ArrayPrototypeSlice(process.argv, 2);
 }
 
+
 /**
  * In strict mode, throw for possible usage errors like --foo --bar
  * @param {object} token - from tokens as available from parseArgs