Better error handling when the configuration file data structure is incorrect

[all-contributors]

Better error handling when the configuration file data structure is incorrect

[Berkmann18]

An approach to this would be:

try {
  JSON.parse(config);
} catch (err) {
  // auto-fix and/or log errors if it can't fix it
}

There are some interesting solutions in this SO post (although most are for only fixing quote issues).

https://jsontuneup.com/ might be a helpful example.

In any case, this comes down to the CLI dependency not being able to parse a malformed configuration file. I started looking into that and found a decent library that provides much more informative errors and which I'm currently exploiting to see if I can get an auto-fixer into the mix.

[jakebolam]

This also broke the schema. Specifying invalid contribution types in the JSON. See sentry: https://sentry.io/organizations/all-contributors/issues/957977140/events/50916998062/