--no-config does not stop config file from being loaded

I've got the following:

const argv = yargs.options({
  config: {
    string: true,
    config: true,
    default: 'mypackagerc'
  },
  myValue: { string: true }
});

This is working well, except that if I do --no-config, the config is still loaded if a file matching the default value exists.
It seems that config might be handled before the --no, as config is set to a value of false but properties from the mypackagerc are still loaded in.

configParser is also not passed the false value, so I can't detect it that way.

Start by tracing the yargs option-parsing path and the configParser entry point described in the report. Reproduce the snippet with --no-config and a present mypackagerc file; done means the file is not loaded and its properties are not added when the option is false.