How to handle other environments like Electron

[joesepi]

See: #1 (comment)

[joesepi]

In the latest meeting, @darcyclarke said @ruyadorno may have some work done on this bit ("main args")

[joesepi]

It would perhaps make sense to just pull in what yargs does as @bcoe had pointed out in the original comment. See that implementation here:
https://github.com/yargs/yargs/blob/master/lib/utils/process-argv.ts

[shadowspawn]

For interest, Commander issues for other environments (I am a maintainer for Commander):

• Electron feedback from > 10 users (including likes)
  • Commander incorrectly assumes that process.argv[0] is 'nodejs' and argv[1] is script name tj/commander.js#512
• zx feedback from 1 user
  • Running a stand-alone subcommand with zx tj/commander.js#1592

(And have not had issues about where to slice in node --eval context, but that seems more likely to come up for something built into node. 😄 )

[shadowspawn]

Moved forward status quo in #20