parserConfiguration "strip-aliased" causes "coerce" not be applied for expanded-camelcase

[gomain]

$ node -e 'const p = require("yargs")(["--n-e", "1"]).option("n-e", { coerce: n => n + 1}).parserConfiguration({ "strip-aliased": true }).parse(); console.log(p)'
{ _: [], 'n-e': 2, nE: 1, '$0': '' }

without is ok

$ node -e 'const p = require("yargs")(["--n-e", "1"]).option("n-e", { coerce: n => n + 1}).parse(); console.log(p)'
{ _: [], 'n-e': 2, nE: 2, '$0': '' }

[shadowspawn]

I was not able to reproduce this with yargs-parser@21.1.1

const argv = require('yargs-parser')(["--n-e", "1"], 
    {
        coerce: { 'n-e': n => n + 1 }, 
        // alias: { 'n-e': 'not-ever' },
        configuration: { 
            'strip-aliased': true,
        }
    }
);
console.log(argv)

% node parser.js --n-e 1
{ _: [], 'n-e': 2, nE: 2 }

[shadowspawn]

I can reproduce the issue calling yargs, like in your reproduction steps. I think the bug is downstream in yargs.

[shadowspawn]

Possibly related: #2159

[shadowspawn]

At this point in the parsing, the aliases includes an entry for the camel-case version of the option, and not just the user supplied aliases. This might be the source of the problem.

yargs/lib/yargs-factory.ts

Line 412 in 2b6ba31

if (aliases[keys] && stripAliased !== true) {

{
  aliases: { help: [], version: [], 'n-e': [ 'nE' ], nE: [ 'n-e' ] },
  keys: 'n-e'
}

[shadowspawn]

There were problems mixing coerce with parser configuration which removes keys from argv. I took a more general approach in #2308 to remove assumptions about configuration.