function parseCommand( command ) {
	/* istanbul ignore next */
	if ( Array.isArray( command ) && command.length === 1 ) {
		command = command[0];
	}

	// remove chromium args from the command line
	/* istanbul ignore else */
	if ( manifest && hasOwnProperty.call( manifest, "chromium-args" ) ) {
		const chromiumArgs = manifest[ "chromium-args" ];
		const pos = command.indexOf( chromiumArgs );
		/* istanbul ignore else */
		if ( pos !== -1 ) {
			command = command.slice( 0, pos ) + command.slice( pos + chromiumArgs.length );
		}
	}
	// Remove user data dir parameter from the command line.
	// This is terribly broken on macOS, as NW.js doesn't use quotation marks for paths including
	// a space character here, which means that the string can't be parsed.
	const userDataDir = dirname( dataPath );
	command = command
		.replace( `--user-data-dir=${userDataDir}`, "" )
		.replace( `--user-data-dir="${userDataDir}"`, "" );

	const argv = getParameters( { command }, parameters )
		.slice( 1 )
		// remove known Chromium parameters
		.filter( arg => !argFilters.some( regex => regex.test( arg ) ) )
		// workaround (for now): only accept known application parameters
		.filter( arg => arg[0] !== "-" || argTests.some( test => test( arg ) ) );

	return minimist( argv, minimistOptions );
}
Turns a command line string into a parameter object

NW.js doesn't correctly parse the passed command line from second application starts
and the positions of parameters and their values will get shifted partially. There is nothing
which can be done on the application code side to restore the original parameter order.

Examples:
- When executing `/path/to/executable --launch foo`:
  /path/to/executable --launch --chromium --specific --stuff foo
- When executing `/path/to/executable --launch foo --goto bar --minimize`:
  /path/to/executable --launch --goto --minimize --chromium --specific --stuff foo bar

The Chromium specific parameters are a mix of the custom NW.js chromium-args field and internal
Chromium parameters. Those have to be removed in order to be able to at least restore
single-parameter-and-value usage. Since internal Chromium parameters are unpredictable/unknown,
we're simply removing any parameter with a leading dash that is not defined in the list above.

@param {String} command
@returns {Object}