Commands are not parsed if preceded by --

[l1bbcsg]

Yargs version: 15.0.0 and above, version 14.2.0 is not affected.
#1459 looks like it could have introduced this.

Setup:

require('yargs')
	.array('array')
	.string('string')
	.command(
		'command',
		'does nothing',
		() => {},
		() => console.log('command executed')
	)
	.demandCommand()
	.argv;

node index.js --array foo bar -- command

Causes Not enough non-option arguments: got 0, need at least 1.

-- here is used to break populating array argument, otherwise command would be parsed as one of its values along with foo and bar and not as a command.

As a result it's not possible to put commands after array arguments at all, while other argument types can precede commands, this works fine for example:

node index.js --string foo command

[mleguen]

-- is no longer used in yargs to stop populating arrays, but to stop parsing arguments, as does npm run for example:

npm run script -- scriptarg1 scriptarg2 ... scriptargn

scriptarg1 scriptarg2 ... scriptargn will be passed to script without being parsed by npm.

However, we should fix the documentation, which still indicate -- as a way to stop populating arrays.

[mxl]

So how should we put command after array argument?

[mleguen]

@mxl AFAIK, yargs does not support commands after positionals (array or not), nor commands after array options.

[mxl]

@l1bbcsg @mleguen I found the way to specify command with array argument. Array argument should be specified after command:

node index.js command --array one two