nyc command line include parameter fix

[alpersogukpinar]

nyc command line include parameter was being ignored and package.json nyc/include values were being used everytime.
Fix #82

[coveralls]

Coverage increased (+0.2%) to 96.0% when pulling 0020b37 on alpersogukpinar:master into 86c1c09 on istanbuljs:master.

[bcoe]

@alpersogukpinar nice approach 👍 NYC_CONFIG is a relatively new environment variable; I was passing around 1,000,001 NYC_ prefixed variables, which were simplified into this one config variable.

[bcoe]

I think I'd prefer that we only set include if NYC_CONFIG.include has been found; perhaps pull this object out into an object called defaults; and only set the include key if it's found?

[coveralls]

Coverage increased (+0.2%) to 96.0% when pulling e55b6dc on alpersogukpinar:master into 86c1c09 on istanbuljs:master.

[coveralls]

Coverage increased (+0.2%) to 96.0% when pulling e55b6dc on alpersogukpinar:master into 86c1c09 on istanbuljs:master.

[alpersogukpinar]

@bcoe I had tried to do something similar by setting include = false if process.env.NYC_CONFIG is undefined. I hope, this time I've changed the code as you suggested, if not please be more specific about the change :-)

[bcoe]

@alpersogukpinar haven't forgotten about this, and am hoping to have some OSS cycles in the coming week (have been on a binge working on a new major version of yargs recently).

[bcoe]

@alpersogukpinar merged this into a slightly different branch with tests, will have pull in a second 👍

[bcoe]

@alpersogukpinar could you please give this a try:

npm cache clear; npm i babel-plugin-istanbul@next

I've landed your work, with a couple minor tweaks (including adding a couple tests for us).