Expand .nycrc to process.argv

[jdalton]

I noticed mocha will expand its mocha.opts into process.argv args.
This allows scripts that were --require'd to detect themselves.

Would nyc be open to expanding its config into process.argv args too?

If it's something you all would dig, I'm up for creating a PR.

[bcoe]

@jdalton I really like this idea, I think we'd just need to be smart and figure out how to make it play nice with features like this:

#620

We allow folks to override a few parameters like cwd, but we then assume that a spawned subprocess won't have these parameters overridden ... cwd might be the only edge-case.

[jdalton]

Ah nice! To start nyc could transfer to process.argv the ones it probably won't have problems with then expand as guards or code to handle others is added.

[bcoe]

@jdalton that's not a bad idea, maybe just black-list cwd for starters?

[jdalton]

👌 , I'll work on a PR

Related to yargs/yargs#503 and moxystudio/yargs-unparser

[Rush]

Maybe related? #709

[JaKXz]

Is this still a valid issue? Is it within the scope of nyc or does it belong in an underlying package (yargs)?

[coreyfarrell]

I'd be interested in seeing an example of a module that would use this information from process.argv but I'm leaning towards calling this out of scope for NYC, I don't think we should mess with process.argv.