make opts object not required anymore for .option()

[maxrimue]

Usually, yargs always requires options to be featuring an object for customisation like so:

yargs()
  .option('x', {})
  .argv

This however seemed strange to me, as said customisation never is needed, you can also use options without any further customisation.

This Pull Request removes the check for whether an object is given to allow for declaration of options like this:

yargs()
  .option('x')
  .argv

Why would we do that? Because it the object isn't needed anyway, requiring it makes little sense, and it might be confusing to people. Also, some people (like me) might prefer to write down all options in the yargs configuration to make clear which ones exist, also making yargs list them in the argv object even if not passed.

[bcoe]

@maxrimue love it! sorry I've been slightly AWOL. ETOOMUCHOSS

[bcoe]

@maxrimue want to give this a spin?

npm cache clear; yargs@6.0.0-alpha.1

This feature goes out with the next release 👍