Node CLI options take precedence in latest Node v10

Is this a BUG or a FEATURE REQUEST?:

A bug

What happened:

Passing CLI options to the executable was working fine in Node v8.9.4.

Since upgrading to Node v10.13.0, CLI options (--x) seem to be parsed with Node instead of being passed to the application.

What you expected to happen:

The application receiving the CLI options, not just arguments.

How to reproduce it (as minimally and precisely as possible):

$ echo "console.log(process.argv)" | nexe -t 8.9.4 -o test.exe && test.exe test
-> [ 'path\test.exe', '[stdin]', 'test' ]
$ echo "console.log(process.argv)" | nexe -t 8.9.4 -o test.exe && test.exe --test
-> [ 'path\test.exe', '[stdin]', '--test' ]

$ echo "console.log(process.argv)" | nexe -t 10.13.0 -o test.exe && test.exe test
-> [ 'path\test.exe', '[stdin]', 'test' ]
$ echo "console.log(process.argv)" | nexe -t 10.13.0 -o test.exe && test.exe --test
-> test.exe: bad option: --test

Anything else we need to know?:

Environment

• Platform(OS/Version): Windows 10
• Host Node Version: 10.13.0
• Target Node Version: 8.9.4 and 10.13.0
• Nexe version: 2.0.0-rc.34
• Python Version: 2.7.15

[calebboyd]

They’re cooking, but the project on AppVeyor appears to be down… Unfortunately it triggers the other builds. Not sure when it will get going again. I’ve contacted their support team.

[calebboyd]

They’re there!